[viraptor]

If you want it constantly running, why not make it a proper service in your systemd config? In that way, yeh it exists. You can follow the logs with "journalctl -u ... -f"

[heyoni]

Yea it's not a great idea. I was thinking like for active development, when you have a few things like redis, flask and mitmproxy running all at once.

I'm very lazy.

[viraptor]

You can preconfigure a screen session in that case. `screenrc` allows you to specify what windows are opened at startup and you can bind specific commands to them.

But docker-compose would do this too.