func main() // 1. Load the specific local file // We use godotenv.Load() with the specific filename. err := godotenv.Load(".env.go.local")
STRIPE_API_KEY=sk_test_12345 LOG_LEVEL=debug
: You can explicitly load this specific file using the godotenv package:
Make it easy for new teammates:
Here's an example of how you can structure your project:
You run go run main.go and wonder why your local overrides aren’t working. The solution: alias go run -tags local in your shell.
This leads you to environment variables, a Unix-born standard where your operating system stores key-value pairs outside your application code. In Go, you can access these via os.Getenv("DB_PASS") . But now you have another problem: manually exporting a dozen variables in your terminal session every time you open a new one is tedious and error-prone. .env.go.local
While not an official Go standard library feature, the pattern of using a .env.go.local file has emerged as a best practice among elite Go teams. It bridges the gap between the inflexibility of hardcoded constants and the chaos of global environment variables.
API_BASE_URL=https://api.example.com API_KEY=your_api_key_here
Note: The first file in the list typically takes precedence. Template Files: Always provide a .env.example func main() // 1
When multiple developers work on the same project, the .env.local pattern truly shines. Each developer can maintain their own .env.local file with their personal database credentials, API keys, and debugging preferences—completely isolated from everyone else.
Elias, the Senior DevOps engineer, pressed Enter . The deployment script whirred into action, spitting out lines of white text against the black background. It was 3:00 AM on a Sunday. The startup, Nebula Dynamic , was pushing their v2.0 update—codenamed "Genesis"—before the investors arrived on Monday morning.
func LoadEnv() // Get the current working directory execPath, err := os.Getwd() if err != nil log.Fatal(err) The solution: alias go run -tags local in your shell
In this article, we'll explore the concept of .env.go.local and how it can simplify your local development workflow in Go applications.
Elias leaned back in his chair, the adrenaline fading, leaving him hollow. He had just spent six hours debugging a ghost created by a file that shouldn't exist, put there by his own hand.