New shards proocodile is here!

[zw963]

Procodile

---

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.

GitHub - crystal-china/procodile_cr: 🐊 Run processes in the background (and...

---

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.

Please help to test it.

1. full features work as expected.
2. the MacOS prebuild version is works.

Check release page for download precompiled binary.

[zw963]

Hi, procodile 1.0.20 is there.

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)

Need document for how porting IO.select(...) in ruby Crystal

IO.select was removed since 2017 by this PR. But for users come from ruby, it still not easy to porting exists code into Fiber + Channel, there is still no a detailed document for how to do this, some examples in that PR is only touch the most simple user case. For me, a user use Crystal for half years, still don’t know how to porting following code to Crystal, showing real-life use cases is often not as easy as comments in the PR. Basically, this is a example read non-blocked from several io…

Porting a really Ruby IO.select use case into Crystal

i am current porting a ruby gem like Foreman but things are designed to run in both foreground/background into Crystal, I am quite ensure it is doable, although there are many challenges. Following is one about IO.select, i am not a expect of it, in fact, manipulate it directly rarely, I need help. The original ruby version code is here, following is the copy. def listen loop do # IO.select IOs, timeout 30 seconds io = IO.select([@sp_reader] + @listeners.keys, nil, nil, 30) if…

What is the equivalent of Ruby Process.detach?

Thanks.

Share data cross fiber the the traditional way?

When the Ruby started early, only start one thread thread, we can get it from Thread.main. We can share data in this way: Thread.main["foo"] = "bar" threads = 2.times.map do |i| sleep 0.5 Thread.new(i) do `notify-send \"#{Thread.main["foo"]} #{i}\"` end end threads.each(&:join) We can see “bar1” and “bar2” output in the desktop notification. How to basically same things in Crystal? Thanks.

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.