Django REST API部署至Railway平台时collectstatic报错及CSS丢失问题求助

I’ve dealt with this exact problem when deploying Django apps to Railway—let’s resolve it properly so your CSS loads correctly and the collectstatic error goes away.

The Root Cause #

The error happens because Railway (like Heroku) automatically runs collectstatic during deployment, but your settings.py doesn’t define a STATIC_ROOT path. This setting tells Django where to gather all static files from your apps and project. When you disabled collectstatic, you skipped this step entirely, which is why your CSS vanished.

Step-by-Step Solution #

1. Update Your Static File Settings in settings.py

Add these lines to the static files section of your settings.py:

# Static files (CSS, JavaScript, Images)
STATIC_URL = '/static/'
# Define where collectstatic will gather all static files
STATIC_ROOT = BASE_DIR / 'staticfiles'

# Optional: If you have custom static files in a project-level directory
# STATICFILES_DIRS = [
#     BASE_DIR / 'static',
# ]

• STATIC_ROOT: This is the directory where Django will collect all static assets (from core apps like django.contrib.admin and your own customer app) when collectstatic runs. Railway will serve files from this directory automatically.
• STATICFILES_DIRS: Uncomment and use this only if you have a project-wide static folder (not inside an app) with custom assets.

2. Ensure DEBUG is False in Production

In your Railway environment variables, set DEBUG = False. When DEBUG is True, Django serves static files directly, but this is unsafe for production and will interfere with collectstatic’s behavior. Your current code uses os.getenv('DEBUG'), so just update the environment variable in Railway’s dashboard.

3. Remove the DISABLE_COLLECTSTATIC Environment Variable

Go to your Railway project’s environment variables and delete the DISABLE_COLLECTSTATIC entry. We want Railway to run collectstatic during deployment now that we’ve configured STATIC_ROOT.

Verify the Fix #

1. Commit your updated settings.py to your repository.
2. Push the changes to Railway.
3. Watch the deployment logs—you’ll see collectstatic run successfully this time, gathering all static files into the staticfiles directory.
4. Once deployed, your API/admin pages should load with all CSS intact.

Why This Works #

By setting STATIC_ROOT, you give Django a clear target directory for collecting static assets. Railway’s deployment pipeline will then ensure these files are served correctly to users. Disabling DEBUG ensures Django doesn’t try to serve static files itself (which it shouldn’t in production) and relies on the collected assets instead.

内容的提问来源于stack exchange，提问作者GN Vageesh