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: Changelog.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,13 @@
1
1
# Changelog
2
2
3
-
This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in
4
-
GitLab.
3
+
This file only reflects the changes that are made in this image. Please refer to the upstream GitLab [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md) for the list of changes in GitLab.
*Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `GITLAB_PORT` and other configuration options*
@@ -229,7 +229,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:
@@ -347,7 +347,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:
765
765
766
766
```bash
767
767
docker run --name gitlab -d [OPTIONS] \
768
-
sameersbn/gitlab:14.10.3 app:sanitize
768
+
sameersbn/gitlab:15.0.0 app:sanitize
769
769
```
770
770
771
771
#### Piwik
@@ -2407,7 +2407,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.
@@ -2442,14 +2442,14 @@ you need to prepare the database:
2442
2442
2443
2443
```bash
2444
2444
docker run --name gitlab -it --rm [OPTIONS] \
2445
-
sameersbn/gitlab:14.10.3 app:rake db:setup
2445
+
sameersbn/gitlab:15.0.0 app:rake db:setup
2446
2446
```
2447
2447
2448
2448
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.
@@ -2575,12 +2575,12 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure
2575
2575
2576
2576
> **Note**
2577
2577
>
2578
-
> Upgrading to `sameersbn/gitlab:14.10.3` 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.
2578
+
> Upgrading to `sameersbn/gitlab:15.0.0` 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.
2579
2579
2580
2580
-**Step 1**: Update the docker image.
2581
2581
2582
2582
```bash
2583
-
docker pull sameersbn/gitlab:14.10.3
2583
+
docker pull sameersbn/gitlab:15.0.0
2584
2584
```
2585
2585
2586
2586
-**Step 2**: Stop and remove the currently running image
@@ -2605,7 +2605,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
2605
2605
> **Note**: Since GitLab `8.11.0` you need to provide the `GITLAB_SECRETS_SECRET_KEY_BASE` and `GITLAB_SECRETS_OTP_KEY_BASE` parameters while starting the image. These should initially both have the same value as the contents of the `/home/git/data/.secret` file. See [Available Configuration Parameters](#available-configuration-parameters) for more information on these parameters.
2606
2606
2607
2607
```bash
2608
-
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:14.10.3
2608
+
docker run --name gitlab -d [OPTIONS] sameersbn/gitlab:15.0.0
0 commit comments