We are currently solving the following issue within our repository. Here is the issue text:
--- BEGIN ISSUE ---
Enforce new SECRET_KEY in production environments
The server should refuse to start if the SECRET_KEY does not differ from the default value in our repository.

The importance of this issue depends on whether the Federated Cloud feature is using this key or not.

--- END ISSUE ---

Below are some code segments, each from a relevant file. One or more of these files may contain bugs.
--- BEGIN FILES ---
Path: `backend/cms/apps.py`
Content:
```
1 """
2 Django related class representing a config of an app
3 """
4 from django.apps import AppConfig
5 
6 
7 class CmsConfig(AppConfig):
8     """
9     Class inheriting the django AppConfig
10     """
11 
12     name = 'cms'
13
```
--- END FILES ---

Please first localize the bug based on the issue statement, and then generate a patch according to the `git diff` format fenced by three backticks.

Here is an example:

```diff
diff --git a/examples/server_async.py b/examples/server_async.py
--- a/examples/server_async.py
+++ b/examples/server_async.py
@@ -313,4 +313,4 @@
 
 
 if __name__ == "__main__":
-    asyncio.run(run_async_server("."), debug=True)
+    asyncio.run(run_async_server(), debug=True)
diff --git a/examples/server_sync.py b/examples/server_sync.py
--- a/examples/server_sync.py
+++ b/examples/server_sync.py
@@ -313,5 +313,5 @@
 
 
 if __name__ == "__main__":
-    server = run_sync_server(".")
+    server = run_sync_server()
     server.shutdown()

```

diff --git a/backend/cms/apps.py b/backend/cms/apps.py
--- a/backend/cms/apps.py
+++ b/backend/cms/apps.py
@@ -1,8 +1,12 @@
 """
 Django related class representing a config of an app
 """
+import logging
+import sys
+from django.conf import settings
 from django.apps import AppConfig
 
+logger = logging.getLogger(__name__)
 
 class CmsConfig(AppConfig):
     """
@@ -10,3 +14,8 @@
     """
 
     name = 'cms'
+
+    def ready(self):
+        if settings.SECRET_KEY == '-!v282$zj815_q@htaxcubylo)(l%a+k*-xi78hw*#s2@i86@_' and not settings.DEBUG:
+            logger.error("You are running the Integreat CMS in production mode. Change the SECRET_KEY in the settings.py!")
+            sys.exit(1)

{"golden_diff": "diff --git a/backend/cms/apps.py b/backend/cms/apps.py\n--- a/backend/cms/apps.py\n+++ b/backend/cms/apps.py\n@@ -1,8 +1,12 @@\n \"\"\"\n Django related class representing a config of an app\n \"\"\"\n+import logging\n+import sys\n+from django.conf import settings\n from django.apps import AppConfig\n \n+logger = logging.getLogger(__name__)\n \n class CmsConfig(AppConfig):\n     \"\"\"\n@@ -10,3 +14,8 @@\n     \"\"\"\n \n     name = 'cms'\n+\n+    def ready(self):\n+        if settings.SECRET_KEY == '-!v282$zj815_q@htaxcubylo)(l%a+k*-xi78hw*#s2@i86@_' and not settings.DEBUG:\n+            logger.error(\"You are running the Integreat CMS in production mode. Change the SECRET_KEY in the settings.py!\")\n+            sys.exit(1)\n", "issue": "Enforce new SECRET_KEY in production environments\nThe server should refuse to start if the SECRET_KEY does not differ from the default value in our repository.\r\n\r\nThe importance of this issue depends on whether the Federated Cloud feature is using this key or not.\n", "before_files": [{"content": "\"\"\"\nDjango related class representing a config of an app\n\"\"\"\nfrom django.apps import AppConfig\n\n\nclass CmsConfig(AppConfig):\n    \"\"\"\n    Class inheriting the django AppConfig\n    \"\"\"\n\n    name = 'cms'\n", "path": "backend/cms/apps.py"}], "after_files": [{"content": "\"\"\"\nDjango related class representing a config of an app\n\"\"\"\nimport logging\nimport sys\nfrom django.conf import settings\nfrom django.apps import AppConfig\n\nlogger = logging.getLogger(__name__)\n\nclass CmsConfig(AppConfig):\n    \"\"\"\n    Class inheriting the django AppConfig\n    \"\"\"\n\n    name = 'cms'\n\n    def ready(self):\n        if settings.SECRET_KEY == '-!v282$zj815_q@htaxcubylo)(l%a+k*-xi78hw*#s2@i86@_' and not settings.DEBUG:\n            logger.error(\"You are running the Integreat CMS in production mode. Change the SECRET_KEY in the settings.py!\")\n            sys.exit(1)\n", "path": "backend/cms/apps.py"}]}