Closed ghost closed 5 years ago
It might be nice if plerdall, on detecting no existing conf file, offered to walk the user through 3 or 4 essential questions to create a minimally functional configuration.
Thanks for this! (And I'm very happy you're using my humble project to learn Perl!) I'll aim to take a closer look within the next few days.
Had an opportunity to observe this firsthand when I had reason to instance a new Plerd blog on a fresh machine. Oh dear, how embarrassing! I'll see if I can't address it presently.
Not sure what, if any, adoption of this spec is but someone brought it up on another project so here's a link for your consideration: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
This should be fixed with 7fa1e70f1c4a42427e914f8358e83498ad04a80b, now on the master branch. @e-krup, please confirm at your own convenience?
@tyrosinase I've put that into my reading list. Thank you!
Plerd was overdue for a new release anyway, so I went ahead and shipped it and baked this fix into it. Thanks again for alerting me to it!
The configuration section of the README reads:
plerdall documentation also reads:
However, on a brand new deployment of Plerd, (installed with cpanm) when running plerdall --init or plerdall --init="path/to/some-dir" I get:
(Sorry editing this as I'm troubleshooting to not clutter up the thread)
This fails only if there is no plerd.conf in the directory
plerdall --init
is being run. Eventouch
ing an empty plerd.conf in the directory makes it work. :woman_shrugging:Furthermore, the message that prints after plerd is deployed in a user-defined directory is:
even though plerd.conf is located in and read from
conf/plerd.conf
I would submit a pull request to fix this but I am using this project as a way to learn Perl myself!