Instead of using named pipes for managing the process, a Unix socket is been used, so if required this opens the possibility to manage via a web JSON API the se

Instead of using named pipes for managing the process, a Unix socket is been used, so if required this opens the possibility to manage via a web JSON API the services an example about how to use Nginx for this is here https://immortal.run/post/nginx/ https://immortal.run/post/nginx/ The idea behind was to avoid a developer to deal with a DevOps/operator to just stop/restart services, something useful on staging environments. For starting, stopping a process there is no need to unlink/link a file, this simplifies things a little bit, for example, https://immortal.run/post/ansible/ https://immortal.run/post/ansible/ by only updating the file contents or "touching" the file it can be started or re-started. When following a PID, signals can still be sent to the process, these things become handy while working with a lot of microservices. The docs need to be improved, but any feedback, comments or even desired feature is more than welcome.