[PR #541] Add django-insecure prefix to hardcoded secret key #1147

Open
opened 2026-03-07 21:30:09 -06:00 by GiteaMirror · 0 comments
Owner

Original Pull Request: https://github.com/docker/awesome-compose/pull/541

State: open
Merged: No


Not ideal that this is hardcoded into the example project, but this (Django standard) prefix will at least add a warning if the user runs ./manage.py check --deploy.

**Original Pull Request:** https://github.com/docker/awesome-compose/pull/541 **State:** open **Merged:** No --- Not ideal that this is hardcoded into the example project, but this (Django standard) prefix will at least add a warning if the user runs [`./manage.py check --deploy`](https://docs.djangoproject.com/en/5.1/ref/checks/#security).
GiteaMirror added the pull-request label 2026-03-07 21:30:09 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#1147