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
Since version `2.4.2`, the image builds are being tagged. You can now pull a particular version of redmine by specifying the version number. For example,
110
110
111
111
```bash
112
-
docker pull sameersbn/redmine:6.0.4
112
+
docker pull sameersbn/redmine:6.0.4-1
113
113
```
114
114
115
115
Alternately you can build the image yourself.
@@ -147,7 +147,7 @@ docker run --name=redmine -d \
Here the image will also automatically fetch the `DB_NAME`, `DB_USER` and `DB_PASS` variables from the mysql container as they are specified in the `docker run` command for the mysql container. This is made possible using the magic of docker links and works with the following images:
@@ -322,7 +322,7 @@ docker run --name=redmine -it --rm \
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:
@@ -395,7 +395,7 @@ _Assuming that the memcached server host is 192.168.1.100_
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.
@@ -533,7 +533,7 @@ docker run --name=redmine -d \
@@ -873,7 +873,7 @@ Relaunch the container with the `app:backup:create` argument.
873
873
874
874
```bash
875
875
docker run --name redmine -it --rm [OPTIONS] \
876
-
sameersbn/redmine:6.0.4 app:backup:create
876
+
sameersbn/redmine:6.0.4-1 app:backup:create
877
877
```
878
878
879
879
The backup will be created in the `backups/` folder of the [Data Store](#data-store). You can change the location using the `REDMINE_BACKUPS_DIR` configuration parameter.
@@ -904,7 +904,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
904
904
905
905
```bash
906
906
docker run --name redmine -it --rm [OPTIONS] \
907
-
sameersbn/redmine:6.0.4 app:backup:restore
907
+
sameersbn/redmine:6.0.4-1 app:backup:restore
908
908
```
909
909
910
910
A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -913,7 +913,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
@@ -963,7 +963,7 @@ To upgrade to newer redmine releases, simply follow this 4 step upgrade procedur
963
963
- **Step 1**: Update the docker image.
964
964
965
965
```bash
966
-
docker pull sameersbn/redmine:6.0.4
966
+
docker pull sameersbn/redmine:6.0.4-1
967
967
```
968
968
969
969
- **Step 2**: Stop and remove the currently running image
@@ -985,7 +985,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
985
985
- **Step 4**: Start the image
986
986
987
987
```bash
988
-
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:6.0.4
988
+
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:6.0.4-1
989
989
```
990
990
991
991
When an upgrade is in progress the variable `REDMINE_WAS_UPDATED` will be defined and set to `yes`. This allows easy integration of individual upgrade-steps via `entrypoint.custom.sh`, `pre-install.sh`, and `post-install.sh`.
0 commit comments