Flisk vs process-compose, Overmind and PM2

With a command in every service.json, Flisk runs plain processes without Docker.

Task Flisk Local dev stack process-compose Process runner Overmind Procfile runner PM2 Node process manager
Start all processes
flisk up

Needs a command in each service.json

pm2 start ecosystem.config.js
Preview the start order
Different job, closest command.
process-compose graph
process-compose up --dry-run

graph prints dependencies; --dry-run only validates the config.

Run in the background
No equivalent

flisk up stays in the foreground

Not needed

pm2 start daemonizes apps by default.

List processes and state
Read logs
process-compose process logs api -f
Different job, closest command.
overmind echo

Only for a daemonized Overmind. README shows no per-process filter.

Restart one process
process-compose process restart api
Stop one process
process-compose process stop api
Stop all
overmind quit

Quits a daemonized Overmind.

Terminal UI
Different job, closest command.
flisk ui

Not yet for local processes

process-compose up
process-compose attach

TUI is on by default; -t=false turns it off.

Different job, closest command.
overmind connect api

Opens one process's tmux window, not a dashboard.

Start at boot
pm2 startup
pm2 save

pm2 startup prints a sudo command to run.