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,
109
109
110
110
```bash
111
-
docker pull sameersbn/redmine:5.1.7
111
+
docker pull sameersbn/redmine:5.1.8
112
112
```
113
113
114
114
Alternately you can build the image yourself.
@@ -146,7 +146,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:
@@ -321,7 +321,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:
@@ -390,7 +390,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.
@@ -528,7 +528,7 @@ docker run --name=redmine -d \
@@ -869,7 +869,7 @@ Relaunch the container with the `app:backup:create` argument.
869
869
870
870
```bash
871
871
docker run --name redmine -it --rm [OPTIONS] \
872
-
sameersbn/redmine:5.1.7 app:backup:create
872
+
sameersbn/redmine:5.1.8 app:backup:create
873
873
```
874
874
875
875
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.
@@ -900,7 +900,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
900
900
901
901
```bash
902
902
docker run --name redmine -it --rm [OPTIONS] \
903
-
sameersbn/redmine:5.1.7 app:backup:restore
903
+
sameersbn/redmine:5.1.8 app:backup:restore
904
904
```
905
905
906
906
A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -909,7 +909,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
@@ -959,7 +959,7 @@ To upgrade to newer redmine releases, simply follow this 4 step upgrade procedur
959
959
- **Step 1**: Update the docker image.
960
960
961
961
```bash
962
-
docker pull sameersbn/redmine:5.1.7
962
+
docker pull sameersbn/redmine:5.1.8
963
963
```
964
964
965
965
- **Step 2**: Stop and remove the currently running image
@@ -981,7 +981,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
981
981
- **Step 4**: Start the image
982
982
983
983
```bash
984
-
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:5.1.7
984
+
docker run --name=redmine -d [OPTIONS] sameersbn/redmine:5.1.8
985
985
```
986
986
987
987
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