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
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@@ -233,7 +233,7 @@ Volumes can be mounted in docker by specifying the `-v` option in the docker run
Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the postgresql container as they are specified in the `docker run` command for the postgresql container. This is made possible using the magic of docker links and works with the following images:
@@ -375,7 +375,7 @@ The image can be configured to use an external redis server. The configuration s
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of SMTP parameters that can be specified.
Please refer the [Available Configuration Parameters](#available-configuration-parameters) section for the list of IMAP parameters that can be specified.
In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer.
When changing this mapping, all files and directories in the mounted data volume `/home/git/data` have to be re-owned by the new ids. This can be achieved automatically using the following command:
819
819
820
820
```bash
821
821
docker run --name gitlab -d [OPTIONS] \
822
-
sameersbn/gitlab:17.8.1 app:sanitize
822
+
sameersbn/gitlab:17.8.2 app:sanitize
823
823
```
824
824
825
825
#### Piwik
@@ -2562,7 +2562,7 @@ Execute the rake task to create a backup.
A backup will be created in the backups folder of the [Data Store](#data-store). You can change the location of the backups using the `GITLAB_BACKUP_DIR` configuration parameter.
@@ -2597,14 +2597,14 @@ you need to prepare the database:
2597
2597
2598
2598
```bash
2599
2599
docker run --name gitlab -it --rm [OPTIONS] \
2600
-
sameersbn/gitlab:17.8.1 app:rake db:setup
2600
+
sameersbn/gitlab:17.8.2 app:rake db:setup
2601
2601
```
2602
2602
2603
2603
Execute the rake task to restore a backup. Make sure you run the container in interactive mode `-it`.
Watch the logs and your repositories should be available into your new gitlab container.
@@ -2730,12 +2730,12 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
2730
2730
2731
2731
> **Note**
2732
2732
>
2733
-
> Upgrading to `sameersbn/gitlab:17.8.1` from `sameersbn/gitlab:7.x.x` can cause issues. It is therefore required that you first upgrade to `sameersbn/gitlab:8.0.5-1` before upgrading to `sameersbn/gitlab:8.1.0` or higher.
2733
+
> Upgrading to `sameersbn/gitlab:17.8.2` from `sameersbn/gitlab:7.x.x` can cause issues. It is therefore required that you first upgrade to `sameersbn/gitlab:8.0.5-1` before upgrading to `sameersbn/gitlab:8.1.0` or higher.
2734
2734
2735
2735
- **Step 1**: Update the docker image.
2736
2736
2737
2737
```bash
2738
-
docker pull sameersbn/gitlab:17.8.1
2738
+
docker pull sameersbn/gitlab:17.8.2
2739
2739
```
2740
2740
2741
2741
- **Step 2**: Stop and remove the currently running image
@@ -2761,7 +2761,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
2761
2761
> **Note**: Since Gitlab 13.7 you need to provide the `GITLAB_SECRETS_ENCRYPTED_SETTINGS_KEY_BASE` parameter while starting the image. If not provided, the key will be generated by gitlab. So you can start the image without setting this parameter. But you will lose the key when you shutting down the container without taking a backup of `secrets.yml`.
2762
2762
2763
2763
```bash
2764
-
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:17.8.1
2764
+
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:17.8.2
0 commit comments