
Infisical Has a Free API — Here's How to Manage Secrets Without .env Files
A developer I know committed a .env file with database credentials to GitHub. A bot found it in 12 seconds. By the time he noticed, someone had already dropped his production database. Stop using .env files. Use a secrets manager. What Infisical Offers for Free Infisical free tier: Unlimited secrets across unlimited projects 5 team members End-to-end encryption CLI, SDK, and REST API Integrations with Vercel, Netlify, GitHub Actions, Docker Secret versioning and audit logs Self-host option (open source) Quick Start # Install CLI brew install infisical/get-cli/infisical # Login infisical login # Initialize in your project infisical init # Pull secrets as env vars infisical run -- node server.js # Your app gets DATABASE_URL, API_KEY, etc. without any .env file REST API # Get all secrets for an environment curl 'https://app.infisical.com/api/v3/secrets/raw?workspaceId=YOUR_PROJECT_ID&environment=prod' \ -H 'Authorization: Bearer YOUR_TOKEN' # Create a secret curl -X POST 'https://app.infi
Continue reading on Dev.to DevOps
Opens in a new tab

