Users who are new to Mojolicious might not know that the mojo command, and by extension the yancy command, isn't very useful and that the primary command to interact with their application is to run their application (myapp.pl). Further, without a yancy.conf file, the standalone daemon is basically no more useful than using mojo daemon.
So, if there is no yancy.conf file in the current directory, the yancy command should die with an error explaining that it's the standalone daemon for working with existing databases and must be configured, but also if you're using Yancy as a plugin, you should invoke your application directly.
Users who are new to Mojolicious might not know that the
mojocommand, and by extension theyancycommand, isn't very useful and that the primary command to interact with their application is to run their application (myapp.pl). Further, without ayancy.conffile, the standalone daemon is basically no more useful than usingmojo daemon.So, if there is no
yancy.conffile in the current directory, theyancycommand should die with an error explaining that it's the standalone daemon for working with existing databases and must be configured, but also if you're using Yancy as a plugin, you should invoke your application directly.