TODO List

[zoffixznet]

Hi,

I've been assigned Daemon::Control as part of the CPAN Pull Request Challenge... for July, of which there are just two days left :)

I've looked through RT and GitHub tickets trying to find anything that I could turn into a PR, but so far don't see anything that could be done in a couple of days.

Do you have any suggestions?

Let me know, ZZ

[symkat]

Hi ZZ,

That's great! Yeah, there are a few things that you could work on:

1. Some work was done on https://github.com/symkat/Daemon-Control/pull/54 but it's been left abandoned. The correct expected work flow is that if a single string is given, it is used as the file path, otherwise if an arrayref is used it's used as the arguments to open for each file handle. So ->stderr_file( [ '>', '/file/path' ] ); would open STDERR to /file/path with the truncate option, while ->stderr_file( '|-', 'my_program', quotemeta( qw( -a foo ) ) would open a pipe to my_program -a foo.
2. Documentation -- We should really add a Daemon::Control::Manual and make documentation on accomplishing some stuff. For example:

2.1 https://github.com/symkat/Daemon-Control/pull/77/files - This work on Logging to Syslog

2.2 http://stackoverflow.com/questions/25975668/cant-run-daemoncontrol-perl-script-as-root-inc-not-correct-perlbrew / https://alisterwest.com/code/perl-mojo-daemon-setup these types of solutions for "Running my app as root doesn't get the right environment" 3. Testing! Our tests for this are pretty awful. If you can come up with a better way of testing that would be amazing. 4. One thing I want to accomplish is to move more things into method calls. With the release of the plugin system in 0.1.7 I want it to be easier to change base behavior through Class::Modifiers and Role::Tiny, instead of having to change entire do_* methods to do things. This may be a bit more involved than the two days through and is something I plan to spend a good amount of time thinking about in the next few weeks.

[zoffixznet]

Point _1_ in the list above has been submitted as PR #83

I think this Issue can be left open for any volunteers to see if they could do the remaining points (it might end up being me for some of them; the module looks interesting).