Flask部署至Heroku时，隐私配置变量与.gitignore的管理最佳实践

Great question—this is a super common pitfall when deploying Flask apps to Heroku, and the good news is there’s a straightforward, secure way to handle it without risking your sensitive data. Let’s break this down step by step:

The key principle here is never commit sensitive configuration (like database URLs or API keys) to Git—even private repos. Git history is permanent, and once data is in there, it’s extremely hard to fully erase. Instead, we’ll use separate tools for local development and Heroku production.

1. Local Development Setup #

• Use a .env file to store your local environment variables (e.g., FLASK_DEBUG=1, DATABASE_URL=sqlite:///dev.db, SECRET_KEY=your_dev_secret).
• Add .env to your .gitignore file immediately—this ensures it never gets committed to Git.
• Use the python-dotenv package to auto-load these variables in your Flask app:

  from dotenv import load_dotenv
  import os
  
  # Loads variables from .env only in local development
  load_dotenv()
  
  # Read variables uniformly across all environments
  SECRET_KEY = os.getenv('SECRET_KEY')
  DATABASE_URL = os.getenv('DATABASE_URL')
  

  This keeps your local config isolated and secure.

2. Deploying to Heroku (No .env File Required) #

Heroku has its own built-in system for managing production environment variables—you don’t need to push your local .env file at all:

• Set variables via Heroku CLI: Run these commands in your terminal:

  heroku config:set SECRET_KEY=your_production_secret_key
  heroku config:set DATABASE_URL=your_production_database_url
  # Add other variables like API keys the same way
  

• Set variables via Heroku Dashboard: Log into your Heroku account, navigate to your app, go to Settings, find the Config Vars section, click Reveal Config Vars, and manually add your key-value pairs.
• Push your code to Heroku as normal: git push heroku main. Heroku automatically injects these config variables into your app’s runtime environment, so your existing os.getenv() calls will work perfectly.

3. Best Practices for Sensitive Config Management #

Avoid these dangerous mistakes at all costs:

• ❌ Don’t remove .env from .gitignore: Even private repos are risky—team members might accidentally share history, or you might open-source the project later.
• ❌ Don’t rely on Git for production config: Mixing code and sensitive config violates the principle of separation of concerns and creates unnecessary security risks.

Stick to these proven practices:

• ✅ Keep config and code fully separate: Sensitive data lives only in local .env files and Heroku’s encrypted Config Vars.
• ✅ Use a uniform variable-reading pattern: Your code doesn’t need to distinguish between local and production—os.getenv() works everywhere.
• ✅ Leverage Heroku’s native tools: Heroku’s Config Vars are encrypted at rest and only accessible to your app. You can update them anytime without redeploying code.
• ✅ (Optional) Batch-manage config: If you have many variables, use heroku config:pull to export production config to a local file (e.g., .env.production), but add this file to .gitignore immediately.
• ✅ Handle multiple environments: Create separate Heroku apps for staging and production, each with their own Config Vars, to avoid cross-environment confusion.

内容的提问来源于stack exchange，提问作者Peter Charland