Member-only story

Go Env Configuration Done Right

8 min readMay 15, 2026

Part of the Go Production Series — a collection of opinionated, battle-tested patterns for building Go services in the real world.

Your service deploys fine in staging. In production, it silently connects to the wrong database because DATABASE_URL was never set — it just defaulted to an empty string and sql.Open was happy to accept it. Three hours later, users are writing data to a stale dev instance.

This is the configuration failure mode nobody talks about: not the crash, but the silent misconfiguration. Your service starts, passes health checks, and serves traffic — to the wrong backend.

Getting configuration right in Go means three things: loading it from the right sources, validating it completely at startup, and making it impossible to accidentally log a secret. This article shows you the pattern that does all three.

The Problem With `os.Getenv` Everywhere

Most Go services start with os.Getenv. It works, which is the problem — it works even when it shouldn't:

// Scattered across handlers, middleware, and main.go
db, _ := sql.Open("postgres", os.Getenv("DATABASE_URL"))  // empty string = silent fail
port := os.Getenv("PORT")…

Feildrix

Go Env Configuration Done Right

The Problem With os.Getenv Everywhere

Written by Feildrix

Responses (1)

More from Feildrix

RBAC in Go — From a Hand-Rolled Approach to Casbin

From simple role checks to policy-driven authorization — and knowing when each one is enough.

Go Middleware Pattern Done Right: HTTP Middleware That Composes

Part of the Go Production Series — a collection of opinionated, battle-tested patterns for building Go services in the real world.

Go Logging Done Right: Stop Using fmt.Println in Production

A practical guide to structured, performant, and production-ready logging in Go — from slog to context-aware patterns

Go Error Handling Done Right: Patterns That Scale

Stop copying if err != nil everywhere — here's how to build error handling that actually grows with your codebase

Recommended from Medium

The 30-Minute Linux Server Hardening Baseline I Apply to Everything

Most of the checklist is already done. Here’s the part that isn’t.

So Good News，Go 1.28 Finally Introduces Inferred Composite Literals: A Proposal That Took 11 Years

If you’re a gopher who has been writing Go for a long time, you’ve definitely had this frustrating moment: the compiler knows exactly what…

I Stopped Writing db: Tags in Go — Here’s What I Use Instead

sqlc generates type-safe Go code from your SQL queries — no struct tags, no manual scanning, no runtime mismatches.

Connection Pooling Is State Management: What Go 1.27 Changed in net/http

How I examine HTTP/1 connection reuse across Go 1.26 and Go 1.27, and what it reveals about protocol state, bounded cleanup, and production…

Anthropic Just Shipped Claude 2.0

9 New Features That Make Claude Code More Powerful Than Ever

Go Error Handling Done Right: Patterns That Scale

Stop copying if err != nil everywhere — here's how to build error handling that actually grows with your codebase

Responses (1)

More from Feildrix

RBAC in Go — From a Hand-Rolled Approach to Casbin

From simple role checks to policy-driven authorization — and knowing when each one is enough.

Go Middleware Pattern Done Right: HTTP Middleware That Composes

Part of the Go Production Series — a collection of opinionated, battle-tested patterns for building Go services in the real world.

Go Logging Done Right: Stop Using fmt.Println in Production

A practical guide to structured, performant, and production-ready logging in Go — from slog to context-aware patterns

Go Error Handling Done Right: Patterns That Scale

Stop copying if err != nil everywhere — here's how to build error handling that actually grows with your codebase

Recommended from Medium

The 30-Minute Linux Server Hardening Baseline I Apply to Everything

Most of the checklist is already done. Here’s the part that isn’t.

So Good News，Go 1.28 Finally Introduces Inferred Composite Literals: A Proposal That Took 11 Years

If you’re a gopher who has been writing Go for a long time, you’ve definitely had this frustrating moment: the compiler knows exactly what…

I Stopped Writing db: Tags in Go — Here’s What I Use Instead

sqlc generates type-safe Go code from your SQL queries — no struct tags, no manual scanning, no runtime mismatches.

Connection Pooling Is State Management: What Go 1.27 Changed in net/http

How I examine HTTP/1 connection reuse across Go 1.26 and Go 1.27, and what it reveals about protocol state, bounded cleanup, and production…

Anthropic Just Shipped Claude 2.0

9 New Features That Make Claude Code More Powerful Than Ever

Go Error Handling Done Right: Patterns That Scale

Stop copying if err != nil everywhere — here's how to build error handling that actually grows with your codebase

The Problem With `os.Getenv` Everywhere