You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -781,13 +781,14 @@ Below is the complete list of available options that can be used to customize yo
781
781
| Parameter | Description |
782
782
|-----------|-------------|
783
783
|`DEBUG`| Set this to `true` to enable entrypoint debugging. |
784
+
|`TZ`| Set the container timezone. Defaults to `UTC`. Values are expected to be in Canonical format. Example: `Europe/Amsterdam` See the list of [acceptable values](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). For configuring the timezone of gitlab see variable `GITLAB_TIMEZONE`. |
784
785
|`GITLAB_HOST`| The hostname of the GitLab server. Defaults to `localhost`|
785
786
|`GITLAB_CI_HOST`| If you are migrating from GitLab CI use this parameter to configure the redirection to the GitLab service so that your existing runners continue to work without any changes. No defaults. |
786
787
|`GITLAB_PORT`| The port of the GitLab server. This value indicates the public port on which the GitLab application will be accessible on the network and appropriately configures GitLab to generate the correct urls. It does not affect the port on which the internal nginx server will be listening on. Defaults to `443` if `GITLAB_HTTPS=true`, else defaults to `80`. |
787
788
|`GITLAB_SECRETS_DB_KEY_BASE`| Encryption key for GitLab CI secret variables, as well as import credentials, in the database. Ensure that your key is at least 32 characters long and that you don't lose it. You can generate one using `pwgen -Bsv1 64`. If you are migrating from GitLab CI, you need to set this value to the value of `GITLAB_CI_SECRETS_DB_KEY_BASE`. No defaults. |
788
789
|`GITLAB_SECRETS_SECRET_KEY_BASE`| Encryption key for session secrets. Ensure that your key is at least 64 characters long and that you don't lose it. This secret can be rotated with minimal impact - the main effect is that previously-sent password reset emails will no longer work. You can generate one using `pwgen -Bsv1 64`. No defaults. |
789
790
|`GITLAB_SECRETS_OTP_KEY_BASE`| Encryption key for OTP related stuff with GitLab. Ensure that your key is at least 64 characters long and that you don't lose it. **If you lose or change this secret, 2FA will stop working for all users.** You can generate one using `pwgen -Bsv1 64`. No defaults. |
790
-
|`GITLAB_TIMEZONE`| Configure the timezone for the gitlab application. This configuration does not effect cron jobs. Defaults to `UTC`. See the list of [acceptable values](http://api.rubyonrails.org/classes/ActiveSupport/TimeZone.html). |
791
+
|`GITLAB_TIMEZONE`| Configure the timezone for the gitlab application. This configuration does not effect cron jobs. Defaults to `UTC`. See the list of [acceptable values](http://api.rubyonrails.org/classes/ActiveSupport/TimeZone.html). For settings the container timezone which will effect cron, see variable `TZ`|
791
792
|`GITLAB_ROOT_PASSWORD`| The password for the root user on firstrun. Defaults to `5iveL!fe`. GitLab requires this to be at least **8 characters long**. |
792
793
|`GITLAB_ROOT_EMAIL`| The email for the root user on firstrun. Defaults to `[email protected]`|
793
794
|`GITLAB_EMAIL`| The email address for the GitLab server. Defaults to value of `SMTP_USER`, else defaults to `[email protected]`. |
0 commit comments