release: 3.4.7

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

Changelog.md

@@ -1,5 +1,17 @@
 # Changelog
 
+**3.4.7**
+- redmine: upgrade to v3.4.7
+- Update mysql image
+- Update memcache image
+- Update postgresql image
+- switch to `ubuntu:trusty-20180712` base image
+- renamed `REDMINE_CACHE_DIR` to `REDMINE_ASSETS_DIR`, `REDMINE_BUILD_DIR` to `REDMINE_BUILD_ASSETS_DIR`, `REDMINE_RUNTIME_DIR` to `REDMINE_RUNTIME_ASSETS_DIR`
+- upgrade to `ubuntu:xenial-20180705`
+- Add: IMAP configuration parameter PROJECT_FROM_SUBADRESS
+- Fix mysql version in docker-compose-mysql.yml
+- Comment out pam_loginuid.so so cron jobs work
+
 **3.4.6**
 - redmine: upgrade to v3.4.6
 

Dockerfile

@@ -16,7 +16,7 @@ FROM ubuntu:xenial-20180705
 LABEL maintainer="[email protected]"
 
 ENV RUBY_VERSION=2.3 \
-    REDMINE_VERSION=3.4.6 \
+    REDMINE_VERSION=3.4.7 \
     REDMINE_USER="redmine" \
     REDMINE_HOME="/home/redmine" \
     REDMINE_LOG_DIR="/var/log/redmine" \

README.md

@@ -56,7 +56,7 @@ Dockerfile to build a [Redmine](http://www.redmine.org/) container image.
 
 ## Version
 
-Current Version: **sameersbn/redmine:3.4.6**
+Current Version: **sameersbn/redmine:3.4.7**
 
 *P.S.: If your installation depends on various third party plugins, please stick with 2.6.xx series to avoid breakage.*
 
@@ -104,7 +104,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:3.4.6
+docker pull sameersbn/redmine:3.4.7
 ```
 
 Alternately you can build the image yourself.
@@ -141,7 +141,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 **NOTE**: Please allow a minute or two for the Redmine application to start.
@@ -186,7 +186,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 ## Database
@@ -236,7 +236,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -281,7 +281,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 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:
@@ -311,7 +311,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -356,7 +356,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 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:
@@ -379,7 +379,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 ### Linking to Memcached Container
@@ -398,7 +398,7 @@ Now you can link memcached to the redmine image:
 
 ```bash
 docker run --name=redmine -it --rm --link=memcached-redmine:memcached \
-  sameersbn/redmine:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 ### Mail
@@ -411,7 +411,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 If you are not using google mail, then please configure the SMTP host and port using the `SMTP_HOST` and `SMTP_PORT` configuration parameters.
@@ -493,7 +493,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 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.
@@ -509,7 +509,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@@ -528,7 +528,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 ### Deploy to a subdirectory (relative url root)
@@ -541,7 +541,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 Redmine will now be accessible at the `/redmine` path, e.g. `http://www.example.com/redmine`.
@@ -557,7 +557,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:3.4.6
+  sameersbn/redmine:3.4.7
 ```
 
 ### Available Configuration Parameters
@@ -721,7 +721,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:3.4.6 \
+  sameersbn/redmine:3.4.7 \
   app:rake redmine:plugins:migrate NAME=plugin_name VERSION=0
 ```
 
@@ -738,7 +738,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:3.4.6 \
+  sameersbn/redmine:3.4.7 \
   app:rake redmine:plugins:migrate NAME=recurring_tasks VERSION=0
 rm -rf /srv/docker/redmine/redmine/plugins/recurring_tasks
 ```
@@ -818,7 +818,7 @@ Relaunch the container with the `app:backup:create` argument.
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:3.4.6 app:backup:create
+  sameersbn/redmine:3.4.7 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.
@@ -849,7 +849,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:3.4.6 app:backup:restore
+  sameersbn/redmine:3.4.7 app:backup:restore
 ```
 
 A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -858,7 +858,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:3.4.6 app:backup:restore BACKUP=1417624827_redmine_backup.tar
+  sameersbn/redmine:3.4.7 app:backup:restore BACKUP=1417624827_redmine_backup.tar
 ```
 
 ## Automated backups
@@ -877,7 +877,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:3.4.6 app:rake redmine:email:test[admin]
+  sameersbn/redmine:3.4.7 app:rake redmine:email:test[admin]
 ```
 
 You can also use `docker exec` to run rake tasks on running redmine instance. For example,
@@ -890,7 +890,7 @@ Similarly, to remove uploaded files left unattached
 
 ```bash
 docker run --name=redmine -d [OPTIONS] \
-  sameersbn/redmine:3.4.6 app:rake redmine:attachments:prune
+  sameersbn/redmine:3.4.7 app:rake redmine:attachments:prune
 ```
 
 Or,
@@ -908,7 +908,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:3.4.6
+docker pull sameersbn/redmine:3.4.7
 ```
 
 - **Step 2**: Stop and remove the currently running image
@@ -930,7 +930,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:3.4.6
+docker run --name=redmine -d [OPTIONS] sameersbn/redmine:3.4.7
 ```
 
 ## Shell Access
@@ -941,6 +941,22 @@ For debugging and maintenance purposes you may want access the containers shell.
 docker exec -it redmine bash
 ```
 
+# Development
+
+## Upgrading to next redmine release
+
+Commands to run to update image to next redmine release, examples are from 3.4.6 to 3.4.7
+
+```bash
+sed -i 's/3.4.6/3.4.7/' VERSION README.md docker-compose-mysql.yml Dockerfile docker-compose.yml
+vim Changelog.md # Update change log
+make
+make release
+sudo rm -rf /srv/docker/redmine/ # Clean old run
+docker-compose down
+docker-compose up # Test new build
+```
+
 # References
     * http://www.redmine.org/
     * http://www.redmine.org/projects/redmine/wiki/Guide

VERSION

@@ -1 +1 @@
-3.4.6
+3.4.7

docker-compose-mysql.yml

@@ -11,7 +11,7 @@ services:
     - /srv/docker/redmine/mysql:/var/lib/mysql
 
   redmine:
-    image: sameersbn/redmine:3.4.6
+    image: sameersbn/redmine:3.4.7
     depends_on:
     - mysql
     environment:

docker-compose.yml

@@ -11,7 +11,7 @@ services:
     - /srv/docker/redmine/postgresql:/var/lib/postgresql
 
   redmine:
-    image: sameersbn/redmine:3.4.6
+    image: sameersbn/redmine:3.4.7
     depends_on:
     - postgresql
     environment: