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

Open
opened 2026-05-31 08:48:35 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/541
Author: @weslord
Created: 12/22/2024
Status: 🔄 Open

Base: master ← Head: django-insecure-key


📝 Commits (1)

  • aca3c76 Add django-insecure prefix to hardcoded secret key

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 django/app/example/settings.py (+1 -1)

📄 Description

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.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/541 **Author:** [@weslord](https://github.com/weslord) **Created:** 12/22/2024 **Status:** 🔄 Open **Base:** `master` ← **Head:** `django-insecure-key` --- ### 📝 Commits (1) - [`aca3c76`](https://github.com/docker/awesome-compose/commit/aca3c764c731b60095bb766cd3554cc0a5f10264) Add django-insecure prefix to hardcoded secret key ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `django/app/example/settings.py` (+1 -1) </details> ### 📄 Description 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). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-31 08:48:35 -05: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#10678