Re:Python Application Deployment with Native Packages
by cageface on Friday May 04, 2012 @03:44AM
(#3927477)
I've said this before here but I think the ability of Go to create a server as a single statically linked binary is a HUGE deployment advantage. It's so much easier to just compile exactly what you want and push out a single file.
[ Parent
| on HN ]
Re:Python Application Deployment with Native Packages
by hynek on Friday May 04, 2012 @03:46AM
(#3927483)
Does it also help with deployment of non-code related files (eg. static files in web apps)?
Re:Python Application Deployment with Native Packages
by nakkiel on Friday May 04, 2012 @09:00AM
(#3928152)
Definitely a problem in Go. It's still possible to embed resources in the binary but if you're talking about a lot of such resources, the resulting binary size can be an issue as well. Not to mention resources won't be available outside of the binary.
Re:Python Application Deployment with Native Packages
by stock_toaster on Friday May 04, 2012 @02:20PM
(#3929633)
I don't think it is any more of a problem with Go than any statically compiled C/C++ binary.
You would still want to use chef, puppet, or some home rolled package deployment toolchain, if for no other reason than being able to ensure a consistent state and bring up new nodes quickly.
Re:Python Application Deployment with Native Packages
by cageface on Friday May 04, 2012 @06:37AM
(#3927822)
No but I think the dependencies among those files tends to be less intricate and brittle than code.
Re:Python Application Deployment with Native Packages
by hynek on Friday May 04, 2012 @07:14AM
(#3927888)
It’s not necessarily about dependencies but about having one self-contained file (= deb/rpm) that can be deployed easily.
The idea about doing this kindled when we started deploying Django apps – you can see in the second example that it’s rather intricate. The dependencies are just a matter of `pip install -r requirements.txt`.