process-compose

Assuming I've found the right process-compose [1], it struck me as having much overlap with the features of systemd. Or at least, I would tend to reach for systemd if I wanted something to run arbitrary processes. Is there something additional/better that process-compose does for you? [1]: https://github.com/F1bonacc1/process-compose

> But so what? Docker is an integral part of the workflow for tons of developers. We use it to be able to run different versions of MySQL, Redis, and ElasticSearch for different applications on the same machine at the same time. You can't really do that without Docker. Nix + Process Compose[0] make a great combo, and runs completely native. [0]: https://github.com/F1bonacc1/process-compose

I've used tmux like that a bunch before discovering process-compose [1]. Still use tmux a lot with remote connections and booting up a few scripts in parallel is still easier with it, but for longer-serving setups p-c has helped a lot [1] https://github.com/F1bonacc1/process-compose

My suggestion would be Process Compose[1]. Just write a simple config telling it what commands to run; it will launch them all and give you a nice TUI to read the stdout and control each process individually. [1] https://github.com/F1bonacc1/process-compose

The IMO superior https://github.com/F1bonacc1/process-compose project has this built in, while allowing to manage regular programs that don't require containers. See: https://f1bonacc1.github.io/process-compose/health/?h=port#r...

Devbox can also run services too. Both products use an awesome process runner called process-compose (https://github.com/f1bonacc1/process-compose/) which is worth checking out (it's even built with nix!)

I've been using https://github.com/F1bonacc1/process-compose with great success. It's a userspace process orchestrator/scheduler that works across all relevant platforms, supporting daemon processes and k8s style readiness/health checks. In combination with nix flakes, it quickly reduced my projects docker-compose usage for easy-to-configure services. This gave huge performance benefits for the M1 Mac folks on my team especially for CPU intensive processes thanks to native binaries. For maximal ease of use, the remaining docker-compose containers are started/stopped as a process-compose task. Quite meta :)