godotenv

Unfortunately, there is tooling, and a subculture that builds tooling, that uses configuration files in the same directory as the source code. Say you're deploying with cool-deploy-tool. cool-deploy-tool finds the password for the server by looking for a file called "Coolfile" in the project root. You have to create that file to use it. Now you have a footgun lying around. I associate this stuff with the Ruby community, but it's spread far and wide, notably to the Node and Go communities, which i think have large Ruby emigrant populations. As a prototypal example, consider dotenv, which began in Ruby: https://github.com/bkeepers/dotenv And has travelled to Node: https://github.com/motdotla/dotenv And Go: https://github.com/joho/godotenv

I've been using wercker to test and auto deploy a few sideproject go apps and the process has been really smooth. I'm about to switch one over to their new ssh deploy stuff and will write a blog post about it. Using them as a plain CI/badge system for libraries is really nice too: I'm using them on https://github.com/joho/godotenv for that and have been really happy with that. Two thumbs up from me for the service all round.