faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
feepbot has quit [Ping timeout: 268 seconds]
feepbot has joined #amber
feepbot has quit [Ping timeout: 268 seconds]
feepbot has joined #amber
<FromGitter> <waghanza> hi, is there a recommanded way to run a `amber` app in background
<FromGitter> <waghanza> i mean using `systemd` or anything like this
feepbot has quit [Ping timeout: 268 seconds]
feepbot has joined #amber
<FromGitter> <Blacksmoke16> docker is pretty nice
snsei has joined #amber
<robacarp> a systemd unit would be pretty straightforward -- amber doesn't fork or anything
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
<FromGitter> <elorest> Systemd is really straight forward to setup if you understand systemd. That's what we use for amberframework.org.
snsei has joined #amber
snsei has quit [Ping timeout: 260 seconds]
feepbot has quit [Read error: Connection reset by peer]
snsei has joined #amber
feepbot has joined #amber
snsei has quit [Ping timeout: 250 seconds]
feepbot has quit [Ping timeout: 246 seconds]
feepbot has joined #amber
feepbot has quit [Ping timeout: 250 seconds]
feepbot has joined #amber
snsei has joined #amber
snsei has quit [Ping timeout: 252 seconds]