# Install pre-commit pre-commit install If you must share a .secrets file via email or cloud storage, use GPG (GNU Privacy Guard) or age encryption. Do not use password-protected ZIP files (they are trivial to crack). Rule 5: The .secrets.template Pattern Instead of committing a real .secrets file, commit a .secrets.template file.
Instead, use (in Swarm mode) or Kubernetes Secrets . You mount the .secrets file as a temporary, in-memory filesystem (tmpfs) that never touches the disk.
# .secrets.template DATABASE_PASSWORD=<your-local-password> API_KEY=<get-from-vault> The developer copies .secrets.template to .secrets and fills in the blanks. The template contains no real secrets, so it is safe in Git. The .secrets file is a bridge technology. It is human-readable, easy to debug, and works everywhere. But the industry is moving toward ephemeral secrets and OIDC (OpenID Connect) . .secrets
Where do you store the keys to your digital kingdom? The database password, the API token for your payment gateway, the private SSH key for production—you can’t hardcode them into your application (that’s a nightmare). You can’t store them in a spreadsheet (that’s chaos). So, the industry landed on a quiet, unassuming, yet incredibly powerful convention: the file.
Here is the professional workflow for .secrets : The developer never touches the production .secrets file. Instead, they authenticate with the Vault using their SSO (Single Sign-On). The Vault generates a temporary .secrets file locally for development only , filled with dummy or low-privilege data. 2. The CI/CD Injection In your pipeline (e.g., GitHub Actions), you do not store the .secrets file in the repo. Instead, you store each secret as an encrypted Repository Secret . During the build, the pipeline reads the encrypted variables and dynamically creates a .secrets file inside the ephemeral container. # Install pre-commit pre-commit install If you must share a
Treat it carelessly—commit it to GitHub, email it around, log it to the console—and you are handing the keys to your kingdom to every bot scanning the internet. Treat it professionally—use a vault, rotate keys, ignore it from Git—and it becomes an invisible shield protecting your users' data.
# .github/workflows/deploy.yml - name: Create .secrets file run: | echo "DATABASE_PASSWORD=$ secrets.DB_PASS " >> .secrets echo "API_KEY=$ secrets.API_KEY " >> .secrets For containers, you never want the .secrets file baked into the Docker image. If someone downloads your image, they get your keys. Instead, use (in Swarm mode) or Kubernetes Secrets
However, we are not there yet. For the next five years, every developer will still touch a .secrets file. It is the last line of defense between your code and a catastrophic data breach. The .secrets file is tiny, unassuming, and dangerously powerful. It demands respect.