Re:Cross compilation just got better in Go 1.5
by TylerE on Monday March 02, 2015 @11:34PM
(#9136116)
Just use something like supervisord: http://supervisord.org/
Super easy to setup - way easier than manually writing init scripts - and it'll handle things like auto-restarting the process if it dies (if you want it to).
It also supports dependency chaining (e.g. before starting the web service, start the DB)
Re:Cross compilation just got better in Go 1.5
by rebelnz on Tuesday March 03, 2015 @12:54AM
(#9136316)
I concur - just set up a couple of sites (written in go) and use Supervisor - its a nice tool and pretty intuitive. Using conf file to specify run app as particular user, set environment variables, logs, autostart etc.. - good to have in one place.
Re:Cross compilation just got better in Go 1.5
by wtf_is_up on Monday March 02, 2015 @11:49PM
(#9136159)
Yeah. I use systemd if the target env already has it, otherwise supervisord does a fine job.
Re:Cross compilation just got better in Go 1.5
by bsaul on Tuesday March 03, 2015 @02:22AM
(#9136502)
Go includes a really good http lib that you can use to handle incoming http connexions. So really, my whole deployment for now is one apt-get for postrges, a golang binary and one json file for configuration, period.
For the service itself i wrote a basic init.d file, but i'll probably use something better ( i see supervisor mentionned, i'll try that).
I mean in _theory_ setting up a Django webserver is just a ./manage.py runsrever but in practice there's a lot of stuff to fix up