1 # GoDotEnv [![Build Status](https://travis-ci.org/joho/godotenv.svg?branch=master)](https://travis-ci.org/joho/godotenv) [![Build status](https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4?svg=true)](https://ci.appveyor.com/project/joho/godotenv) [![Go Report Card](https://goreportcard.com/badge/github.com/joho/godotenv)](https://goreportcard.com/report/github.com/joho/godotenv)
3 A Go (golang) port of the Ruby dotenv project (which loads env vars from a .env file)
5 From the original Library:
7 > Storing configuration in the environment is one of the tenets of a twelve-factor app. Anything that is likely to change between deployment environments–such as resource handles for databases or credentials for external services–should be extracted from the code into environment variables.
9 > But it is not always practical to set environment variables on development machines or continuous integration servers where multiple projects are run. Dotenv load variables from a .env file into ENV when the environment is bootstrapped.
11 It can be used as a library (for loading in env for your own daemons etc) or as a bin command.
13 There is test coverage and CI for both linuxish and windows environments, but I make no guarantees about the bin version working on windows.
20 go get github.com/joho/godotenv
23 or if you want to use it as a bin command
25 go get github.com/joho/godotenv/cmd/godotenv
30 Add your application configuration to your `.env` file in the root of your project:
33 S3_BUCKET=YOURS3BUCKET
34 SECRET_KEY=YOURSECRETKEYGOESHERE
37 Then in your Go app you can do something like
43 "github.com/joho/godotenv"
49 err := godotenv.Load()
51 log.Fatal("Error loading .env file")
54 s3Bucket := os.Getenv("S3_BUCKET")
55 secretKey := os.Getenv("SECRET_KEY")
57 // now do something with s3 or whatever
61 If you're even lazier than that, you can just take advantage of the autoload package which will read in `.env` on import
64 import _ "github.com/joho/godotenv/autoload"
67 While `.env` in the project root is the default, you don't have to be constrained, both examples below are 100% legit
70 _ = godotenv.Load("somerandomfile")
71 _ = godotenv.Load("filenumberone.env", "filenumbertwo.env")
74 If you want to be really fancy with your env file you can do comments and exports (below is a valid env file)
77 # I am a comment and that is OK
79 FOO=BAR # comments at line end are OK too
83 Or finally you can do YAML(ish) style
90 as a final aside, if you don't want godotenv munging your env you can just get a map back instead
93 var myEnv map[string]string
94 myEnv, err := godotenv.Read()
96 s3Bucket := myEnv["S3_BUCKET"]
99 ... or from an `io.Reader` instead of a local file
102 reader := getRemoteFile()
103 myEnv, err := godotenv.Parse(reader)
106 ... or from a `string` if you so desire
109 content := getRemoteFileContent()
110 myEnv, err := godotenv.Unmarshal(content)
115 Assuming you've installed the command as above and you've got `$GOPATH/bin` in your `$PATH`
118 godotenv -f /some/path/to/.env some_command with some args
121 If you don't specify `-f` it will fall back on the default of loading `.env` in `PWD`
123 ### Writing Env Files
125 Godotenv can also write a map representing the environment to a correctly-formatted and escaped file
128 env, err := godotenv.Unmarshal("KEY=value")
129 err := godotenv.Write(env, "./.env")
135 env, err := godotenv.Unmarshal("KEY=value")
136 content, err := godotenv.Marshal(env)
141 Contributions are most welcome! The parser itself is pretty stupidly naive and I wouldn't be surprised if it breaks with edge cases.
143 *code changes without tests will not be accepted*
146 2. Create your feature branch (`git checkout -b my-new-feature`)
147 3. Commit your changes (`git commit -am 'Added some feature'`)
148 4. Push to the branch (`git push origin my-new-feature`)
149 5. Create new Pull Request
153 Releases should follow [Semver](http://semver.org/) though the first couple of releases are `v1` and `v1.1`.
155 Use [annotated tags for all releases](https://github.com/joho/godotenv/issues/30). Example `git tag -a v1.2.1`
159 Linux: [![Build Status](https://travis-ci.org/joho/godotenv.svg?branch=master)](https://travis-ci.org/joho/godotenv) Windows: [![Build status](https://ci.appveyor.com/api/projects/status/9v40vnfvvgde64u4)](https://ci.appveyor.com/project/joho/godotenv)
163 The original library [dotenv](https://github.com/bkeepers/dotenv) was written by [Brandon Keepers](http://opensoul.org/), and this port was done by [John Barton](https://johnbarton.co/) based off the tests/fixtures in the original library.