Re:REST Servers in Go: Part 1 – standard library
by zemo on Sunday January 17, 2021 @12:47AM
(#25808498)
running python servers is annoying, you have to have a menagerie of stupid little parts and things to get it all to fit together. I haven't done this in years but I always wound up with some mess of virtual envs, pip, gunicorn, nginx proxying, something to start the services, and that's _before_ writing any of my own code. With Go I just compile a static binary, rsync it to a server and turn it on and call it a day. The only other part I often use is nginx as a reverse proxy because it's easier to harden. Way easier to operate and way easier to not break once your project gets beyond a few kloc.
[ Parent
| on HN ]
Re:REST Servers in Go: Part 1 – standard library
by bartvk on Sunday January 17, 2021 @08:49AM
(#25810592)
> With Go I just compile a static binary, rsync it to a server and turn it on
With "turning it on", you mean you write a systemd configuration file and start it using systemctl, right? Just curious how people do this stuff nowadays.