Manage Secrets in Local Development (without .env)
For years, developers have relied on .env files, SOPS files, and other ad-hoc processes to manage secrets in local development. But as projects and teams grow, it gets messy pretty fast — files go out of sync across environments, get shared in insecure ways, and become prone to leaking.
In this video, I show a cleaner approach to managing environment variables in local development using Infisical.
We’ll walk through setup step-by-step: Logging in with the CLI, initializing a project with Infisical, and injecting secrets straight into your runtime — no .env files required.
I demo the workflow with Node.js but the same approach works with almost any stack including Flask, Django, Spring Boot, Laravel, Ruby on Rails, and more.
Outline:
0:00 Intro
1:12 Begin Tutorial
2:19 Adding secrets to Infisical
3:28 Injecting secrets at runtime with the Infisical CLI
5:22 Wrap up
Links:
Infisical: https://infisical.com
Infisical CLI: https://infisical.com/docs/cli/usage
Follow Infisical:
Website: https://infisical.com
LinkedIn: / infisical
GitHub: https://github.com/Infisical
Twitter / X: https://x.com/infisical
Slack: https://infisical.com/slack
Follow Tony:
LinkedIn: / tony-d-a104a6125
GitHub: https://github.com/dangtony98
Twitter / X: https://x.com/dangtony98