Dopbase guides

Secrets management and safer AI coding.

We write practical guidance for developers handling application secrets, plus honest notes about the decisions behind Dopbase. Product examples use the current Dopbase command-line interface.

September 27, 2026

dotenv Explained: Complete Guide for Developers

Learn how dotenv loads .env files in Node.js, validate environment variables, fix common errors, and move from local files to Dopbase runtime injection.

An .env file feeds configuration values through a loader into an application on a laptop.

September 26, 2026

How to share .env variables securely with your team

Compare secure ways to share .env variables with your team, from password managers and encrypted files to runtime secret injection with Dopbase.

Three teammates at laptops connect to a shared, locked secrets vault.

September 15, 2026

How to Manage .env Secrets Across Multiple Projects Efficiently

Learn how a solo developer uses Dopbase to manage .env secrets across multiple projects without keeping plaintext copies in every repository.

A solo developer connects three project secret folders to one centralized secure vault.

September 6, 2026

Best Open-Source Secrets Manager Alternative to Doppler

Compare Dopbase and Doppler on open source, self-hosting, pricing, and workflow. Learn when each secrets manager fits your team.

Dopbase and Doppler logos side by side in a secrets manager comparison graphic.

September 4, 2026

Best Open-Source Self-Hosted Secrets Manager for Developers

Looking for the best open-source self-hosted secrets manager? Compare Dopbase with Infisical and see why a focused Rust-based workflow can fit developers.

A flat illustration of a developer connecting to a compact self-hosted secrets manager with separate environment keys.

September 2, 2026

Best Secret Manager Tools for Developers in 2026

Compare the best secret manager tools and learn why Dopbase is the best all-around option to evaluate for a focused, self-hosted workflow.

A flat illustration of a developer laptop connected to a protected file, a secure vault, and cloud secret storage.

September 1, 2026

How to keep secrets out of an AI coding workspace

Use fake values for routine agent work, isolate credentialed tests, and deliver restricted development secrets only after reviewing the code.

A flat illustration with fake keys inside a coding workspace and a real key secured in a locked store outside it.

August 31, 2026

Why development should not use production secrets

Separate development and production credentials so a mistake on a laptop, test runner, or coding agent cannot reach live systems.

A flat illustration of separate development and production areas protected by different keys and a solid boundary.

August 30, 2026

Committed a secret? Revoke it before cleaning Git history

Deleting a committed secret does not disable it or remove it from Git history. Revoke or rotate it first, then clean the repository.

A flat illustration showing an old Git commit with a red key that still opens a lock after the latest file is clean.

August 29, 2026

Can an AI coding agent read your .env file?

Yes, a coding agent can usually read an ignored .env file. Learn where credentials can leak and how to keep real secrets outside its workspace.

A flat illustration of an AI cursor reaching toward a marked .env file inside a developer workspace.

August 28, 2026

Why we're keeping Dopbase's secrets model small

Dopbase uses three concepts: projects, environments, and secrets. We explain why the model stops there.

A flat illustration showing one application divided into environments, with individual keys stored inside each environment.