Heroku与Django静态文件问题：迁移至AWS后部署collectstatic报错

Hey there, let’s work through this collectstatic error you’re facing on Heroku after switching from WhiteNoise to AWS S3 for static and media files. Based on your description, here are the most common fixes to try:

1. Verify Your STATIC_ROOT Configuration #

Heroku’s collectstatic command needs a valid local directory to temporarily gather static files before pushing them to S3. Make sure your settings.py has this set correctly:

import os
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))

STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles')

This directory doesn’t need to exist locally (collectstatic will create it), but ensure the path is accurate—avoid typos that might point to a non-existent location.

2. Double-Check django-storages Setup #

Since you’re using S3, you’re likely relying on django-storages to handle the transfer. Confirm these key settings in settings.py:

• Add 'storages' to INSTALLED_APPS
• Set the storage backends for static and media files:

  STATICFILES_STORAGE = 'storages.backends.s3boto3.S3Boto3Storage'
  DEFAULT_FILE_STORAGE = 'storages.backends.s3boto3.S3Boto3Storage' # Only if media files also go to S3
  

• Ensure your AWS credentials and bucket name are set as environment variables on Heroku. Use these commands to set them if you haven’t:

  heroku config:set AWS_ACCESS_KEY_ID=your-access-key
  heroku config:set AWS_SECRET_ACCESS_KEY=your-secret-key
  heroku config:set AWS_STORAGE_BUCKET_NAME=your-bucket-name
  

Missing or incorrect credentials will prevent collectstatic from pushing files to S3, often triggering file-not-found errors.

3. Check for Missing Static Files in Git #

Heroku deploys directly from your Git repository. If you have static files locally that aren’t committed (e.g., new CSS/JS in an app’s static folder), collectstatic on Heroku won’t find them. Run these commands to fix it:

git add your_app/static/
git commit -m "Add missing static files to repo"
git push heroku main

4. Validate STATICFILES_DIRS #

If you have a project-level static directory (not tied to a specific app), make sure STATICFILES_DIRS in settings.py points to it correctly:

STATICFILES_DIRS = [
    os.path.join(BASE_DIR, 'static'),
]

A typo here can cause collectstatic to look in the wrong place, leading to missing file errors.

5. Test with DISABLE_COLLECTSTATIC (Temporary) #

To confirm the issue is directly related to collectstatic, you can temporarily disable it on Heroku:

heroku config:set DISABLE_COLLECTSTATIC=1

If the deployment succeeds after this, you know the problem lies in your collectstatic/S3 configuration. Remember to remove this setting once you fix the issue—production environments need collectstatic to serve static files properly.

6. Dig Into the Exact Error Message #

The FileNotFound error should specify which file is missing. If it’s a specific app’s static file, verify that app has a static directory with the correct files and is added to INSTALLED_APPS. If it’s a third-party package’s static file, ensure the package is listed in your requirements.txt (Heroku installs packages from this file during deployment).

内容的提问来源于stack exchange，提问作者John Rogerson