gdamore
Samples don't work on Windows
It looks like govisor doesn't work standalone (which is a pity) and govisord won't start.
>govisord.exe
Failed to open services directory services: open services: The system cannot find the file specified.
This is a doc bug. You need to arrange to set up a services directory somewhere, and point govisord at it. Look at the samples directory under govisord -- for a UNIX system you could run govisord -dir ./samples
Unfortunately, that probably won't work at all on Windows, because the samples I've provided assume a POSIX shell. That's not a govisor limitation, but really an issue with being able to create useful test samples in a Windows environment -- its easy to write some trivial shell scripts to demo stuff (for me); I'm not sure how the best way to do this for windows is. Its been decades since I wrote Microsoft batch files (.BAT files for MS-DOS 6.x).
I'd love to accept a PR that added a Windows samples directory here too. :-)
So govisor is something like supervisord, not something like process monitor as I thought originally.
Writing yet another config just to test yet another alternative is bad for user experience. It would be nice if this package could base it demos on existing stuff. I think that foreman/honcho with its Procfiles is also something that this package does. And IIRC it works without deamon, which is useful for development.
So I'm not sure how to cope entirely with this.
The same service, govisord, is a process manager that uses govisor. But govisor itself runs without a daemon, its just a framework. Sadly, govisor (the client) needs to speak REST commands at something, hence the daemon.
Having looked at Procfiles only briefly (I have 0 experience with Heroku, which is where Procfiles seem to come from), it seems to me that their format is rather limited.
That said, we could probably add a trivial importer for procfiles. I'm not sure how valuable that ultimately is. I'm not opposed to this -- just looking for justification before I go off and do the work. Heroku isn't something I'm exposed to in my regular work life.
Procfiles from Heroku may not be the latest best practice - it is just an example of how it could be done with static config.