Add option to run Invoker as daemon #59
Conversation
Stops Invoker if it is running as a daemon.
Processes with relative path should work if Invoker is running as a daemon.
|
Can we rebase this on top of refactor-reactor because constant loading etc changed there. |
…ctor-branch Conflicts: lib/invoker/cli.rb spec/invoker/commander_spec.rb
|
So about a. I think Invoker should log its logs to a file when daemonized. As in What you think? |
|
Do we still need to log when |
|
tail command only sends individual process logs, what if |
|
What happens to the |
|
ah, damn.yeah that is the tricky. Is there a way for existing installations we can move |
Follow the existing pattern of defining accessor methods.
Also move the old .invoker file to ~/.invoker/config
User can tail more than one process at once. Also fixed minor issues with when invoker is not running.
|
One small thing with now ability to daemonize invoker, people can by mistake try and run two invokers. One daemonized one and another non-daemonize one. We should protect them from that. |
Refactored process managment from commander class in its own class.
Also refactor old file migration
This saves from occasional encoding errors
No description provided.