3 ms·
How well does this work in practice? I mean for a web server don't you still have to hook up _something_ in the server (at least to start up the binary)? I mea
by rtpg 12y ago
How well does this work in practice? I mean for a web server don't you still have to hook up _something_ in the server (at least to start up the binary)?
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
- TylerE 12y agoJust use something like supervisord: http://supervisord.org/ 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)
- wtf_is_up 12y agoYeah. I use systemd if the target env already has it, otherwise supervisord does a fine job.
- rebelnz 12y agoI 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.
- bsaul 12y agoGo 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).