release: 4.0.4

Signed-off-by: Cormier, Jonathan <[email protected]>

Changelog.md

@@ -1,5 +1,8 @@
 # Changelog
 
+**4.0.4**
+- redmine: upgrade to v4.0.4
+
 **4.0.3-2**
 - Fix logrotate. Issue #402
 

Dockerfile

@@ -16,7 +16,7 @@ FROM ubuntu:xenial-20190222
 LABEL maintainer="[email protected]"
 
 ENV RUBY_VERSION=2.4 \
-    REDMINE_VERSION=4.0.3 \
+    REDMINE_VERSION=4.0.4 \
     REDMINE_USER="redmine" \
     REDMINE_HOME="/home/redmine" \
     REDMINE_LOG_DIR="/var/log/redmine" \

README.md

@@ -58,7 +58,7 @@ Dockerfile to build a [Redmine](http://www.redmine.org/) container image.
 
 ## Version
 
-Current Version: **sameersbn/redmine:4.0.3-2**
+Current Version: **sameersbn/redmine:4.0.4**
 
 *P.S.: If your installation depends on various third party plugins, please stick with 2.6.xx series to avoid breakage.*
 
@@ -106,7 +106,7 @@ docker pull sameersbn/redmine:latest
 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,
 
 ```bash
-docker pull sameersbn/redmine:4.0.3-2
+docker pull sameersbn/redmine:4.0.4
 ```
 
 Alternately you can build the image yourself.
@@ -143,7 +143,7 @@ docker run --name=redmine -d \
   --link=postgresql-redmine:postgresql --publish=10083:80 \
   --env='REDMINE_PORT=10083' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 **NOTE**: Please allow a minute or two for the Redmine application to start.
@@ -188,7 +188,7 @@ Volumes can be mounted in docker by specifying the **'-v'** option in the docker
 ```bash
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 ## Database
@@ -238,7 +238,7 @@ docker run --name=redmine -it --rm \
   --env='DB_HOST=192.168.1.100' --env='DB_NAME=redmine_production' \
   --env='DB_USER=redmine' --env='DB_PASS=password' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -283,7 +283,7 @@ We are now ready to start the redmine application.
 ```bash
 docker run --name=redmine -it --rm --link=mysql-redmine:mysql \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 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:
@@ -313,7 +313,7 @@ docker run --name=redmine -it --rm \
   --env='DB_HOST=192.168.1.100' --env='DB_NAME=redmine_production' \
   --env='DB_USER=redmine' --env='DB_PASS=password' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -358,7 +358,7 @@ We are now ready to start the redmine application.
 ```bash
 docker run --name=redmine -it --rm --link=postgresql-redmine:postgresql \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 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:
@@ -381,7 +381,7 @@ The image can be configured to use an external memcached server. The memcached s
 ```bash
 docker run --name=redmine -it --rm \
   --env='MEMCACHE_HOST=192.168.1.100' --env='MEMCACHE_PORT=11211' \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 ### Linking to Memcached Container
@@ -400,7 +400,7 @@ Now you can link memcached to the redmine image:
 
 ```bash
 docker run --name=redmine -it --rm --link=memcached-redmine:memcached \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 ### Mail
@@ -413,7 +413,7 @@ Please refer the [Available Configuration Parameters](#available-configuration-p
 docker run --name=redmine -it --rm \
   --env='[email protected]' --env='SMTP_PASS=PASSWORD' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 If you are not using google mail, then please configure the SMTP host and port using the `SMTP_HOST` and `SMTP_PORT` configuration parameters.
@@ -495,7 +495,7 @@ docker run --name=redmine -d \
   --publish=10083:80 --publish 10445:443 \
   --env='REDMINE_PORT=10445' --env='REDMINE_HTTPS=true' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 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.
@@ -511,7 +511,7 @@ docker run --name=redmine -d \
   --env='REDMINE_HTTPS=true' \
   --env='NGINX_HSTS_MAXAGE=2592000'
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@@ -530,7 +530,7 @@ In summation, when using a load balancer, the docker command would look for the
 docker run --name=redmine -d --publish=10083:80 \
   --env='REDMINE_HTTPS=true' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 ### Deploy to a subdirectory (relative url root)
@@ -543,7 +543,7 @@ Let's assume we want to deploy our application to '/redmine'. Redmine needs to k
 docker run --name=redmine -d --publish=10083:80 \
   --env='REDMINE_RELATIVE_URL_ROOT=/redmine' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 Redmine will now be accessible at the `/redmine` path, e.g. `http://www.example.com/redmine`.
@@ -573,7 +573,7 @@ Also the container processes seem to be executed as the host's user/group `1000`
 ```bash
 docker run --name=redmine -it --rm [options] \
   --env="USERMAP_UID=500" --env="USERMAP_GID=500" \
-  sameersbn/redmine:4.0.3-2
+  sameersbn/redmine:4.0.4
 ```
 
 ### Available Configuration Parameters
@@ -737,7 +737,7 @@ To uninstall plugins you need to first tell redmine about the plugin you need to
 ```bash
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2 \
+  sameersbn/redmine:4.0.4 \
   app:rake redmine:plugins:migrate NAME=plugin_name VERSION=0
 ```
 
@@ -754,7 +754,7 @@ For example, to remove the recurring tasks plugin:
 ```bash
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
-  sameersbn/redmine:4.0.3-2 \
+  sameersbn/redmine:4.0.4 \
   app:rake redmine:plugins:migrate NAME=recurring_tasks VERSION=0
 rm -rf /srv/docker/redmine/redmine/plugins/recurring_tasks
 ```
@@ -834,7 +834,7 @@ Relaunch the container with the `app:backup:create` argument.
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:4.0.3-2 app:backup:create
+  sameersbn/redmine:4.0.4 app:backup:create
 ```
 
 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.
@@ -865,7 +865,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:4.0.3-2 app:backup:restore
+  sameersbn/redmine:4.0.4 app:backup:restore
 ```
 
 A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -874,7 +874,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:4.0.3-2 app:backup:restore BACKUP=1417624827_redmine_backup.tar
+  sameersbn/redmine:4.0.4 app:backup:restore BACKUP=1417624827_redmine_backup.tar
 ```
 
 ## Automated backups
@@ -893,7 +893,7 @@ The `app:rake` command allows you to run redmine rake tasks. To run a rake task
 
 ```bash
 docker run --name=redmine -d [OPTIONS] \
-  sameersbn/redmine:4.0.3-2 app:rake redmine:email:test[admin]
+  sameersbn/redmine:4.0.4 app:rake redmine:email:test[admin]
 ```
 
 You can also use `docker exec` to run rake tasks on running redmine instance. For example,
@@ -906,7 +906,7 @@ Similarly, to remove uploaded files left unattached
 
 ```bash
 docker run --name=redmine -d [OPTIONS] \
-  sameersbn/redmine:4.0.3-2 app:rake redmine:attachments:prune
+  sameersbn/redmine:4.0.4 app:rake redmine:attachments:prune
 ```
 
 Or,
@@ -924,7 +924,7 @@ To upgrade to newer redmine releases, simply follow this 4 step upgrade procedur
 - **Step 1**: Update the docker image.
 
 ```bash
-docker pull sameersbn/redmine:4.0.3-2
+docker pull sameersbn/redmine:4.0.4
 ```
 
 - **Step 2**: Stop and remove the currently running image
@@ -946,7 +946,7 @@ Replace `x.x.x` with the version you are upgrading from. For example, if you are
 - **Step 4**: Start the image
 
 ```bash
-docker run --name=redmine -d [OPTIONS] sameersbn/redmine:4.0.3-2
+docker run --name=redmine -d [OPTIONS] sameersbn/redmine:4.0.4
 ```
 
 ## Shell Access
@@ -961,10 +961,10 @@ docker exec -it redmine bash
 
 ## Upgrading to next redmine release
 
-* Commands to run to update image to next redmine release, examples are from 3.4.7 to 4.0.3-2
+* Commands to run to update image to next redmine release, examples are from 3.4.7 to 4.0.4
 
 ```bash
-sed -i 's/4.0.2/4.0.3-2/' VERSION README.md docker-compose-mysql.yml Dockerfile docker-compose.yml
+sed -i 's/4.0.2/4.0.4/' VERSION README.md docker-compose-mysql.yml Dockerfile docker-compose.yml
 vim Changelog.md # Update change log
 sudo rm -rf /srv/docker/redmine/ # Clean old run
 docker-compose down
@@ -978,7 +978,7 @@ git push origin --tags
 ```
 
 * Open https://github.com/sameersbn/docker-redmine/releases and Draft new release
-* Select tag 4.0.3-2 and set release title to 4.0.3
+* Select tag 4.0.4 and set release title to 4.0.3
 * Publish release
 * Check https://quay.io/repository/sameersbn/redmine?tab=info  and https://hub.docker.com/r/sameersbn/redmine/builds for build progress
 

VERSION

@@ -1 +1 @@
-4.0.3-2
+4.0.4

docker-compose-mysql.yml

@@ -12,7 +12,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:4.0.3-2
+    image: sameersbn/redmine:4.0.4
     depends_on:
     - mysql
     environment:

docker-compose.yml

@@ -12,7 +12,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:4.0.3-2
+    image: sameersbn/redmine:4.0.4
     depends_on:
     - postgresql
     environment: