From 5c6060cec4d8c852d15ff50bfbc6fa86eb59168b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Oliver=20G=C3=BCnther?= <o.guenther@openproject.com>
Date: Wed, 13 May 2026 08:26:44 +0200
Subject: [PATCH] Use <your-secret-key-base>

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 43070ba..f5a5354 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ sudo chown 1000:1000 -R /var/openproject/assets
 Next you start up the containers in the background while making sure to pull the latest versions of all used images.
 
 ```shell
-SECRET_KEY_BASE=OVERWRITE_ME OPENPROJECT_HTTPS=false docker compose up -d --build --pull always
+SECRET_KEY_BASE=<your-secret-key-base> OPENPROJECT_HTTPS=false docker compose up -d --build --pull always
 ```
 After a while, OpenProject should be up and running on `http://localhost:8080`. The default username and password is login: `admin`, and password: `admin`.
 The `OPENPROJECT_HTTPS=false` environment variable explicitly disables HTTPS mode for the first startup. Without this, OpenProject assumes it's running behind HTTPS in production by default.