Improve your Dev Stack with process-compose
As developers, we often run multiple services to work on a single project. I've managed my projects with makefiles, PM2, Tmux, Procfiles, and many other solutions. They all had their pros and cons, but none of them felt like the perfect solution. I always kept looking for a "docker (compose) for development environments". The problem with docker itself is that it works fine for a database, but not for something like go or node services, where you want to restart the service on file changes, and use hot reloading.
And that's exactly what it is. It's a single binary that enables you to define your services in a process-compose.yaml file, and then start them all with a single command. It's like docker-compose, but for binaries on your system. Complete with health checks, restarts, and logs like we know from docker-compose, and with support for hot reloading like you depend on in your local development environment.
Before we set things up, let's take a quick look at an example screen from a bigger project of mine. This is what process-compose looks like:
