How to run Erlang/Rebar3 release as a background process

The best solution? Run it using supervisor that will keep it linked to the PID 1 (or other system managed process) so it will:

• be easy to manage, ex. systemctl start myapp/systemctl stop myapp
• will survive VM failures
• will be easily observable, ex. systemctl status myapp
• you will be able to define startup and shutdown requirements and order
• in some cases it can even handle logs for you

Thanks for the response but I am confused as to why it is so difficult to do with the built in rebar3 commands.

Reading their docs they speak of a daemon command which seems ideal but my version of rebar3 does not give me such options.

They also state that production releases should be ran in using the foreground option. Where I would think that it would make sense for a soft realtime system to be ran in the background.

I have tried to run my app using bin/myapp start which does seem to start an Linux OS process but I am unable to connect to my app with a browser when it is started with the start command.

It only seems to work correctly when I use the console or foreground command

Then check out logs, the information what is happening should be somewhere there.