Skip to content

Commit c50029f

Browse files
committed
Update REDMINE_SECRET_KEY_BASE usage/description
1 parent c125332 commit c50029f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

redmine/content.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ This variable allows you to control if `rake redmine:plugins:migrate` is run on
114114

115115
### `REDMINE_SECRET_KEY_BASE`
116116

117-
This variable is required when using Docker Swarm replicas to maintain session connections when being loadbalanced between containers. It will create an initial `config/secrets.yml` and set the `secret_key_base` value, which is "used by Rails to encode cookies storing session data thus preventing their tampering. Generating a new secret token invalidates all existing sessions after restart" ([session store](https://www.redmine.org/projects/redmine/wiki/RedmineInstall#Step-5-Session-store-secret-generation)). If you do not set this variable or provide a `secrets.yml` one will be generated using `rake generate_secret_token`.
117+
This variable is required when using loadbalanced replicas to maintain session connections. It will set the `SECRET_KEY_BASE` environment variable, which is "used by Rails to encode cookies storing session data thus preventing their tampering. Generating a new secret token invalidates all existing sessions after restart" ([session store](https://www.redmine.org/projects/redmine/wiki/RedmineInstall#Step-5-Session-store-secret-generation)). If you do not set this variable, then the `secret_key_base` value will be generated using `rake generate_secret_token`. Alternatively, you can set the `SECRET_KEY_BASE` environment variable directly.
118118

119119
## Running as an arbitrary user
120120

0 commit comments

Comments
 (0)