Django static assets site deploy fails

1

I’m trying to create a static site for my static file assets in Django. The process works as expected (static files are generated, but then Render says that the deploy failed? It’s not returning any useful debugging output so I’m at a loss for how to debug.

Build output

(snipped for brevity)
Jan 24 04:37:34 PM  Requirement already satisfied: wrapt==1.13.3 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 55)) (1.13.3)
Jan 24 04:37:34 PM  Requirement already satisfied: setuptools>=20.0 in ./.venv/lib/python3.10/site-packages (from astroid==2.9.3->-r requirements.txt (line 3)) (59.6.0)
Jan 24 04:37:40 PM  Using production.py settings...
Jan 24 04:37:40 PM  224 static files copied to '/opt/render/project/src/STATIC_ROOT', 596 post-processed.

The last line is exactly what I expect to see on success. However, I instead see:
Screenshot 2022-01-24 164921

Build Script

#!/usr/bin/env bash
set -o errexit

pip install --upgrade pip
pip install wheel
pip install -r requirements.txt
python manage.py collectstatic --no-input

and the important bit in the render.yaml file:

- type: web
    name: Static Assets
    env: static
    buildCommand: "./build_static.sh"
    staticPublishPath: ./STATIC_ROOT
    headers:
      - path: /*
        name: X-Frame-Options
        value: sameorigin
    domains:
      - static.wp-poweranalytics.com
    envVars:
      - key: ENV
        value: PRODUCTION
      - key: PYTHON_VERSION
        value: 3.10.1
2

Hi Jack,

“Exited with Status 1” means that your build command returned an unsuccessful exit code. Is it possible that an error was returned after generating the files but before the end of the script?

3

There doesn’t appear to be an issue. I’ve added additional flags --traceback which will throw a stack trace if something goes wrong during static file processing and also -v 3 to increase the verbosity to max. No errors are showing up.

Do I need to explicitly exit the build_static.sh script with a safe exit code?

4

Could you share the service ID that is having this issue?