chore: Remove .env.production file and update documentation for environment file security

This commit is contained in:
William Valentin
2025-09-06 10:52:45 -07:00
parent fb26939a9a
commit 75d0f772e9
4 changed files with 19 additions and 43 deletions

View File

@@ -45,10 +45,17 @@
#### **Environment Variables**
- Never commit `.env` files to version control
- Use separate environment files for different deployments
- Rotate credentials regularly
- Use strong, unique passwords for each environment
- Never commit `.env` files to version control, especially `.env.production` which contains production credentials
- Use `.env.example` as a template for creating new environment files
- Create separate environment files for different deployment environments:
- `.env` - Local development
- `.env.staging` - Staging environment
- `.env.production` - Production environment
- Always add all `.env` files to `.gitignore` to prevent accidental commits
- Use environment variables for configuration to maintain security and flexibility
- Rotate credentials regularly and use strong, unique passwords for each environment
- Consider using a secrets management system for production environments
- Never hardcode sensitive information in source code
#### **Docker Security**