s6 VS PM2

This page and this page, both by Laurent Bercot, creator of s6. Source: about 1 year ago

Of the two I have experience with, runit is simpler and thus easier to get the hang of than s6-rc/s6. Though the s6 (not s6-rc) docs at the author's site contain a lot of info (including apologetics and rationales) that applies almost equally well to runit. Source: about 1 year ago

Using the s6-service add command I added a service called "libvertd" when I ment to put "libvirtd". Now when I run s6-db-reload it spits out a error message saying "undefined service name libvertd". But I cant remove it using s6-service remove libvertd because that just spits out a generic help message and doesn't change anything. I also couldn't find documentation on Https://skarnet.org/software/s6/ or... Source: over 1 year ago

For the trivia, this is pushed by Laurent Bercot (skarnet), creator of s6, execline and many others. He's also working on implementing s6 as Alpine init and rc systems. https://skarnet.org/software/s6/ https://skarnet.com/projects/service-manager.html. - Source: Hacker News / over 1 year ago

FWIW, the spirit of daemontools lives on in the s6 project. https://skarnet.org/software/s6/. - Source: Hacker News / almost 2 years ago

Meet PM2, the process manager that’s here to make your deployment woes disappear. It helps you manage your Node.js processes like a boss, ensuring everything runs smoothly in production. With features like clustering, load balancing, and centralized logging, PM2 is like having a command center for your applications. It's the kind of tool that makes you wonder how you ever lived without it. - Source: dev.to / 22 days ago

Then go to your project dir, and install packages via npm or yarn, then build your app. After that, install pm2 to run your app (forever):. - Source: dev.to / 4 months ago

PM2 is a daemon process manager that will help you manage and keep your application online 24/7. It has a lot of features that will help you in the process of deploying and maintaining your application. - Source: dev.to / 10 months ago

1) Perhaps these limitations are relevant in the gaming industry, but for web applications, 4GB of memory seems sufficient to me, especially on the frontend where a single user performs multiple tasks. As for multithreading, we can utilize tools like pm2 and load balancing. Additionally, developing a multithreaded program is typically more challenging than creating a single-threaded program and executing it across... Source: 11 months ago

I recently moved to using Docker as my "process manager," after using pm2 for a couple years to manage 5-10 random apps/APIs. Even for fairly simple stuff (and definitely as you go from medium complexity on up), Docker is superior in my opinion - easy workflow for updating from a Git repo (git pull && docker compose up --build -d is all you need most of the time), system packages (e.g. C/C++ library headers) are... Source: 11 months ago