|
etatoby posted:If by "package management" you mean the fact that you have to pull all the sources for the libraries you use inside your project's source tree, or use your version control "linked repo" feature, and then it compiles everything down to a static binary that you can deploy anywhere, then I believe Go has the best package management I've ever seen. Are you using any of the 3rd party dependency management tools? Or checking in your entire GOPATH? It's a little frustrating that One True Way hasn't emerged yet, and I'm just not doing enough go development to be able to judge the competitors.
|
# ¿ Jul 16, 2014 18:39 |
|
|
# ¿ May 3, 2024 15:11 |
|
sarehu posted:I have a question for you Go people. Suppose you write a web application in Go. What do you do to get it running in actual production? Running the Go process on a higher, unprivileged port and proxying is the way to do it. Look into something more powerful than nohup for running your code, though. I use daemontools at work and it's fine, but I think supervisor is a bit more reasonable to set up. You want something that will handle stdout/stderr redirection, restarting the process when it crashes, and reporting on process status.
|
# ¿ Mar 15, 2015 03:36 |