Devise主密码配置：Heroku生产环境构建故障求助

Hey there! Let's break down how to resolve this Devise master password problem you're facing on Heroku, especially with your Compose-hosted SSL database. Since you’ve already pinpointed a potential root cause, I’ll zero in on the most common culprits tied to your setup:

1. Verify Environment Variable for Devise Master Password #

First, double-check that your Devise master password is properly set in Heroku’s environment variables. Local development often uses .env files, but Heroku doesn’t auto-load those.

• Run this command to confirm the variable exists (replace DEVISE_MASTER_PASSWORD with your actual variable name):

  heroku config:get DEVISE_MASTER_PASSWORD
  

• If it’s missing, set it with:

  heroku config:set DEVISE_MASTER_PASSWORD=your_secure_master_password
  

• Make sure the variable name matches exactly what you’re using in your Devise initializer (e.g., config.master_password = ENV["DEVISE_MASTER_PASSWORD"]).

2. Ensure Database SSL Configuration is Correct for Compose #

Compose requires SSL for database connections, and Rails production environments sometimes need explicit SSL settings that local dev might skip.

• Open your config/database.yml and update the production section to include SSL parameters specific to Compose:

  production:
    adapter: postgresql # or your database adapter
    url: <%= ENV['DATABASE_URL'] %>
    sslmode: require
    sslrootcert: config/ca-certificates.crt # Make sure this file is committed to your repo!
  

• Compose usually provides a CA certificate file—download it, place it in your config folder, and commit it to Git so Heroku can access it during deployment.
• If you’re using a different adapter (like MySQL), adjust the SSL settings accordingly (e.g., sslca, sslcert as needed).

3. Check Devise Initialization Order in Production #

Sometimes production precompilation or eager loading can cause Devise to load before your environment variables are fully available.

• Modify your config/initializers/devise.rb to ensure the master password is loaded after environment variables:

  Rails.application.config.after_initialize do
    Devise.setup do |config|
      config.master_password = ENV["DEVISE_MASTER_PASSWORD"]
      # rest of your Devise config...
    end
  end
  

• This ensures that Rails has fully loaded all environment variables before Devise sets up the master password.

4. Confirm Rails Secret Key Base is Properly Set #

Devise relies on Rails’ encryption system, and a missing or incorrect secret_key_base can cause unexpected authentication issues in production.

• Verify the key is set:

  heroku config:get SECRET_KEY_BASE
  

• If not, generate a new one and set it:

  rake secret
  heroku config:set SECRET_KEY_BASE=generated_secret_key
  

5. Debug Deployment Build Failures #

If the build itself is failing (not just runtime), check the Heroku build logs for specific errors:

• Run this to view recent build logs:

  heroku logs --tail --source build
  

• Look for errors related to database connections, missing files (like the CA cert), or environment variable issues. For example, if the build is trying to run migrations before SSL is configured, you might need to set DISABLE_DATABASE_ENVIRONMENT_CHECK=1 temporarily for migrations (only do this if you’re sure it’s safe).

Once you’ve addressed these areas, redeploy your app to Heroku with git push heroku main (or your default branch) and test the master password login again.

内容的提问来源于stack exchange，提问作者Novneet Nov