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
feepbot has quit [Ping timeout: 245 seconds]
_whitelogger has joined #amber
_whitelogger has joined #amber
fyber has joined #amber
_whitelogger has joined #amber
<FromGitter> <elorest> @damianham We're doing something similar. Just create a new timestamped binary, start it on the same port and kill the other one after it's running. That has worked well for me.
_whitelogger has joined #amber
_whitelogger has joined #amber
_whitelogger has joined #amber
<FromGitter> <elorest> I've spent the last week playing with Rust Langs Rocket Framework. A few cool things there but it's crazy how much further Amber and technically even Lucky are along toward actually being useful at your day job.
<FromGitter> <drujensen> @elorest I will try it out
_whitelogger has joined #amber
_whitelogger has joined #amber
<FromGitter> <damianham> @drujensen thanks for that info, snap looks like an interesting option so I will check it out. @elorest I currently download the new binary to a temp file, unlink the running binary then rename the temp binary. The new binary starts on reboot. I suppose a better option would be to run systemctl restart.
feepbot has joined #amber
vivus has joined #amber
vivus has quit [Remote host closed the connection]