1. Deploying using git. (git repo on the server with git init --bare and
placing a hook to build and copy files)
2. Deploying using "Capistrano" - Seems more like a standard.
3. Deploying using some configuration management system like puppet or
chef .. Build a package (rpm or deb), and update it via the CMS.
But is there a "Go" method that's being used and that I'm missing out ?
Or is it like - "It's a language. You find your own way to mess around your
Problems I face:
1. Go is not installed on all servers where the application will be
deployed. So compilation on all servers is a bad idea
2. Development System architecture and flavor is different from deploy
system architecture and flavor. Would you recommend go-cross-compile for
production use ?
3. It's not going to be a single file. Say it's a webapp, then there are
configuration files, static files, templates, etc.. which needs to be
bundled together too, and all these make things complicated.
Need some help finding a work-around for solving these issues.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.