3 ms·

> But I'm inclined to agree that this is one area Go projects have a hard time with. The portability of the executable is great, but if you're doing anything th

> But I'm inclined to agree that this is one area Go projects have a hard time with. The portability of the executable is great, but if you're doing anything that requires static assets, configuration, or data outside the context of the runtime, you can easily end up with a tough-to-manage mess of configuration. This is mostly a sysadmin/devops issue, since all languages have the same issue. I solve it through a CM tool (Ansible, in my case) that sets up my directories, rsyncs my templates and TOML config, and uploads my binary. Not having to worry the server running the same env as my dev environment removes a whole class of bugs/frustration.

serverhorror 12y ago
> This is mostly a sysadmin/devops issue, since all languages have the same issue. You're kidding right? I thought that whole "devops" movement (call it what you like) was to get rid of the attitude of "other people's problem". I live in environments that are (for the most part) regulated and demand by law that there is a strict separation between the people running and developing software, often open to interpretation is the 3rd role of people configuring the software. The problem is that "I solve it..." just doesn't work. Either people solve it by working cooperatively together or it simply won't ever be deployed. There's no such thing as a sysadmin problem, devops problem, developer problem. (No go downvote me for the tone of the next sentence) -- For me it's either get your ass moving, stand up, walk over to people and talk to them or get lost!
- elithrar 12y ago
  I missed this at the time, but I think you read past what I said: I used "devops" in the tools sense, not the people sense. A programming language (the syntax, the compiler, the linter) can't be everything to everyone, and therefore most don't attempt to shoehorn in things like static asset bundling, etc. That's why frameworks exist, or packages like go-bindata or rakyll/statik (https://github.com/rakyll/statik https://github.com/rakyll/statik), or CM tools that can wrap it all together.

serverhorror 12y ago

> This is mostly a sysadmin/devops issue, since all languages have the same issue. You're kidding right? I thought that whole "devops" movement (call it what you like) was to get rid of the attitude of "other people's problem". I live in environments that are (for the most part) regulated and demand by law that there is a strict separation between the people running and developing software, often open to interpretation is the 3rd role of people configuring the software. The problem is that "I solve it..." just doesn't work. Either people solve it by working cooperatively together or it simply won't ever be deployed. There's no such thing as a sysadmin problem, devops problem, developer problem. (No go downvote me for the tone of the next sentence) -- For me it's either get your ass moving, stand up, walk over to people and talk to them or get lost!

elithrar 12y ago
I missed this at the time, but I think you read past what I said: I used "devops" in the tools sense, not the people sense. A programming language (the syntax, the compiler, the linter) can't be everything to everyone, and therefore most don't attempt to shoehorn in things like static asset bundling, etc. That's why frameworks exist, or packages like go-bindata or rakyll/statik (https://github.com/rakyll/statik https://github.com/rakyll/statik), or CM tools that can wrap it all together.