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:7.0.0-1
112
+
docker pull sameersbn/redmine:7.0.0-2
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 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:
@@ -334,7 +334,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.
@@ -472,7 +472,7 @@ docker run --name=redmine -d \
@@ -805,7 +805,7 @@ Relaunch the container with the `app:backup:create` argument.
805
805
806
806
```bash
807
807
docker run --name redmine -it --rm [OPTIONS] \
808
-
sameersbn/redmine:7.0.0-1 app:backup:create
808
+
sameersbn/redmine:7.0.0-2 app:backup:create
809
809
```
810
810
811
811
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.
@@ -836,7 +836,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
836
836
837
837
```bash
838
838
docker run --name redmine -it --rm [OPTIONS] \
839
-
sameersbn/redmine:7.0.0-1 app:backup:restore
839
+
sameersbn/redmine:7.0.0-2 app:backup:restore
840
840
```
841
841
842
842
A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -845,7 +845,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
@@ -895,7 +895,7 @@ To upgrade to newer redmine releases, simply follow this 4 step upgrade procedur
895
895
- **Step 1**: Update the docker image.
896
896
897
897
```bash
898
-
docker pull sameersbn/redmine:7.0.0-1
898
+
docker pull sameersbn/redmine:7.0.0-2
899
899
```
900
900
901
901
- **Step 2**: Stop and remove the currently running image
@@ -917,7 +917,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
917
917
- **Step 4**: Start the image
918
918
919
919
```bash
920
-
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:7.0.0-1
920
+
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:7.0.0-2
921
921
```
922
922
923
923
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