Running & deploying Ruby apps to places like Viaduct & Heroku is really easy but running processes on actual servers is less fun. Procodile aims to take some the stress out of running your Ruby/Rails apps and give you some of the useful process management features you get from the takes of the PaaS providers.
Procodile is a bit like Foreman but things are designed to run in the background (as well as the foreground if you prefer) and there’s a supervisor which keeps an eye on your processes and will respawn them if they die.
Procodile works out of the box with your existing Procfile.
This is a Crystal fork for Ruby(original) version, with some minor bug fixes.
Although most of the process is just copying/pasting, But, It’s still not an easy process.
Although it’s just a small version upgrade, but usability has been greatly improved.
Before this version, there a issue has been ongoing for a long time, the process log output is not print(yes, i use my this procodile fork in the production for years, but without process log output …)
I ask some questions in the form for help (links may be incomplete)
Some of them answered, some of them not, but all of them give me lots of inspiration from those discussion, but, no process log output issue always is there, no any progress, porting a ruby gem over 2000 LOC is not easy.
Certainly, I know it now, this issue related to many things, Fiber, Channel, Socket, Process, Serialize … etc, I even couldn’t find where is the real issue is when I asked the question.
Anyway, i fixed it, there are many refactor work need to be done in following weeks, but at least, the functionality compare to orignal ruby version is complete.
Welcome try it, and give me feedback, thanks!
BTW: special thanks to David Yoteau, it mention this tool in his talk for CrystalConf 2023, even at that time, there was no process log output, it’s let me know there is someone else using it besides me, this is my source of drive me going on.
