Skip to content

Update Dockerfile #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
heshanlk merged 1 commit into from
Sep 13, 2026
Merged

Update Dockerfile #96

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,16 @@
# Build Tailwind CSS
RUN cd theme/static_src && npm ci && npm run build

# Collect static files
# Collect static files. INBOX_AI_ENABLED is forced on here (independent of
# the runtime env var) so apps.inbox_ai is registered and its assets land in
# the manifest — otherwise enabling the feature at runtime 404s/500s on
# inbox_ai/reply.css because whitenoise's manifest is immutable after build.
RUN DJANGO_SETTINGS_MODULE=config.settings.production \
SECRET_KEY=build-placeholder \
DATABASE_URL=sqlite:///tmp/build.db \
INBOX_AI_ENABLED=True \
python manage.py collectstatic --noinput

EXPOSE 8000

CMD gunicorn config.wsgi:application --bind 0.0.0.0:${PORT:-8000} --workers 2 --threads 2

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / Docker build

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/