Indexed by TopGit from live GitHub metadata: joho/godotenv has 10.7k stars, written primarily in Go. A Go port of Ruby's dotenv library (Loads environment variables from .env files)
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
A Go (golang) port of the Ruby dotenv project (which loads env vars from a .env file).
From the original Library:
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.
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.
It can be used as a library (for loading in env for your own daemons etc.) or as a bin command.
There is test coverage and CI for both linuxish and Windows environments, but I make no guarantees about the bin version working on Windows.
Installation
As a library
go get github.com/joho/godotenv
as a tool dependency:
go >= 1.24
go get -tool github.com/joho/godotenv/cmd/godotenv
or if you want to use it as a bin command
go install github.com/joho/godotenv/cmd/godotenv@latest
Usage
Add your application configuration to your .env file in the root of your project:
Ruby's dotenv only allows [A-Za-z0-9_.] in key names, while Node's dotenv also permits -. godotenv has matched the Node charset since v1.4.0, so keys like MY-VAR parse cleanly here and in Node but will error under Ruby's dotenv.
Precedence & Conventions
Existing envs take precedence of envs that are loaded later.
The convention
for managing multiple environments (i.e. development, test, production)
is to create an env named {YOURAPP}_ENV and load envs in this order:
env := os.Getenv("FOO_ENV")
if "" == env {
env = "development"
}
godotenv.Load() // The Original .env
godotenv.Load(".env." + env)
if "test" != env {
godotenv.Load(".env.local")
}
godotenv.Load(".env." + env + ".local")
If you need to, you can also use godotenv.Overload() to defy this convention
and overwrite existing envs instead of only supplanting them. Use with caution.
Command Mode
Assuming you've installed the command as above and you've got $GOPATH/bin in your $PATH
godotenv -f /some/path/to/.env some_command with some args
If you don't specify -f it will fall back on the default of loading .env in PWD
By default, it won't override existing environment variables; you can do that with the -o flag.
Writing Env Files
Godotenv can also write a map representing the environment to a correctly-formatted and escaped file
This library has been declared feature complete (see #182 for background) and will not be accepting issues or pull requests adding new functionality or breaking the library API.
Contributions would be gladly accepted that:
bring this library's parsing into closer compatibility with the mainline dotenv implementations, in particular Ruby's dotenv and Node.js' dotenv
keep the library up to date with the go ecosystem (ie CI bumps, documentation changes, changes in the core libraries)
bug fixes for use cases that pertain to the library's purpose of easing development of codebases deployed into twelve factor environments
code changes without tests and references to peer dotenv implementations will not be accepted
Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Added some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request
Releases
Releases should follow Semver though the first couple of releases are v1 and v1.1.
Use annotated tags for all releases. Example git tag -a v1.2.1
Who?
The original library dotenv was written by Brandon Keepers, and this port was done by John Barton based off the tests/fixtures in the original library.
The most recent commit recorded on joho/godotenv was 4 months ago, based on the GitHub push timestamp. The repository has 468 forks — one of the better signals of community interest.
Is joho/godotenv open source?
Yes — joho/godotenv ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/joho/godotenv.
What license does joho/godotenv use?
joho/godotenv is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
What topics is joho/godotenv associated with?
GitHub's repository topics for joho/godotenv: "dotenv", "environment-variables", "go", "golang". TopGit's editorial category is Backend.
Where can I see joho/godotenv in action?
The project maintains a homepage at http://godoc.org/github.com/joho/godotenv. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about joho/godotenv?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/joho/godotenv is the definitive source.
Read full README in the tab above.
Curious whether godotenv is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about godotenv.