release: 5.1.2

Signed-off-by: Jonathan Cormier <jcormier@criticallink.com>

Changelog.md

@@ -1,5 +1,9 @@
 # Changelog
 
+**5.1.2**
+- redmine: upgrade to v5.1.2
+- Remove bundler version pin
+
 **5.1.1-5**
 - Only update file-permissions when needed on server start #547
 

README.md

@@ -60,7 +60,7 @@ Dockerfile to build a [Redmine](http://www.redmine.org/) container image.
 
 ## Version
 
-Current Version: **sameersbn/redmine:5.1.1-5**
+Current Version: **sameersbn/redmine:5.1.2**
 
 _P.S.: If your installation depends on various third party plugins, please stick with 2.6.xx series to avoid breakage._
 
@@ -108,7 +108,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:5.1.1-5
+docker pull sameersbn/redmine:5.1.2
 ```
 
 Alternately you can build the image yourself.
@@ -146,7 +146,7 @@ docker run --name=redmine -d \
   --env='REDMINE_PORT=10083' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 **NOTE**: Please allow a minute or two for the Redmine application to start.
@@ -193,7 +193,7 @@ Volumes can be mounted in docker by specifying the **'-v'** option in the docker
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 ## Database
@@ -244,7 +244,7 @@ docker run --name=redmine -it --rm \
   --env='DB_USER=redmine' --env='DB_PASS=password' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -290,7 +290,7 @@ We are now ready to start the redmine application.
 docker run --name=redmine -it --rm --link=mysql-redmine:mysql \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 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 \
   --env='DB_USER=redmine' --env='DB_PASS=password' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 This will initialize the redmine database and after a couple of minutes your redmine instance should be ready to use.
@@ -367,7 +367,7 @@ We are now ready to start the redmine application.
 docker run --name=redmine -it --rm --link=postgresql-redmine:postgresql \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 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_
 ```bash
 docker run --name=redmine -it --rm \
   --env='MEMCACHE_HOST=192.168.1.100' --env='MEMCACHE_PORT=11211' \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 ### Linking to Memcached Container
@@ -409,7 +409,7 @@ Now you can link memcached to the redmine image:
 
 ```bash
 docker run --name=redmine -it --rm --link=memcached-redmine:memcached \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 ### Mail
@@ -423,7 +423,7 @@ docker run --name=redmine -it --rm \
   --env='SMTP_USER=USER@gmail.com' --env='SMTP_PASS=PASSWORD' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 If you are not using google mail, then please configure the SMTP host and port using the `SMTP_HOST` and `SMTP_PORT` configuration parameters.
@@ -509,7 +509,7 @@ docker run --name=redmine -d \
   --env='REDMINE_PORT=10445' --env='REDMINE_HTTPS=true' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 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 \
   --env='NGINX_HSTS_MAXAGE=2592000'
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 If you want to completely disable HSTS set `NGINX_HSTS_ENABLED` to `false`.
@@ -548,7 +548,7 @@ docker run --name=redmine -d --publish=10083:80 \
   --env='REDMINE_HTTPS=true' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 ### Deploy to a subdirectory (relative url root)
@@ -562,7 +562,7 @@ docker run --name=redmine -d --publish=10083:80 \
   --env='REDMINE_RELATIVE_URL_ROOT=/redmine' \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 Redmine will now be accessible at the `/redmine` path, e.g. `http://www.example.com/redmine`.
@@ -593,7 +593,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:5.1.1-5
+  sameersbn/redmine:5.1.2
 ```
 
 ### Available Configuration Parameters
@@ -769,7 +769,7 @@ To uninstall plugins you need to first tell redmine about the plugin you need to
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5 \
+  sameersbn/redmine:5.1.2 \
   app:rake redmine:plugins:migrate NAME=plugin_name VERSION=0
 ```
 
@@ -787,7 +787,7 @@ For example, to remove the recurring tasks plugin:
 docker run --name=redmine -it --rm \
   --volume=/srv/docker/redmine/redmine:/home/redmine/data \
   --volume=/srv/docker/redmine/redmine-logs:/var/log/redmine/ \
-  sameersbn/redmine:5.1.1-5 \
+  sameersbn/redmine:5.1.2 \
   app:rake redmine:plugins:migrate NAME=recurring_tasks VERSION=0
 rm -rf /srv/docker/redmine/redmine/plugins/recurring_tasks
 ```
@@ -867,7 +867,7 @@ Relaunch the container with the `app:backup:create` argument.
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:5.1.1-5 app:backup:create
+  sameersbn/redmine:5.1.2 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.
@@ -898,7 +898,7 @@ Relaunch the container with the `app:backup:restore` argument. Ensure you launch
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:5.1.1-5 app:backup:restore
+  sameersbn/redmine:5.1.2 app:backup:restore
 ```
 
 A list of existing backups will be displayed. Select a backup you wish to restore.
@@ -907,7 +907,7 @@ To avoid this interaction you can specify the backup filename using the `BACKUP`
 
 ```bash
 docker run --name redmine -it --rm [OPTIONS] \
-  sameersbn/redmine:5.1.1-5 app:backup:restore BACKUP=1417624827_redmine_backup.tar
+  sameersbn/redmine:5.1.2 app:backup:restore BACKUP=1417624827_redmine_backup.tar
 ```
 
 ## Automated backups
@@ -926,7 +926,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:5.1.1-5 app:rake redmine:email:test[admin]
+  sameersbn/redmine:5.1.2 app:rake redmine:email:test[admin]
 ```
 
 You can also use `docker exec` to run rake tasks on running redmine instance. For example,
@@ -939,7 +939,7 @@ Similarly, to remove uploaded files left unattached
 
 ```bash
 docker run --name=redmine -d [OPTIONS] \
-  sameersbn/redmine:5.1.1-5 app:rake redmine:attachments:prune
+  sameersbn/redmine:5.1.2 app:rake redmine:attachments:prune
 ```
 
 Or,
@@ -957,7 +957,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:5.1.1-5
+docker pull sameersbn/redmine:5.1.2
 ```
 
 - **Step 2**: Stop and remove the currently running image
@@ -979,7 +979,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:5.1.1-5
+docker run --name=redmine -d [OPTIONS] sameersbn/redmine:5.1.2
 ```
 
 ## Shell Access
@@ -994,10 +994,10 @@ docker exec -it redmine bash
 
 ## Upgrading to next redmine release
 
-- Commands to run to update image to next redmine release, examples are from 5.0.4 to 5.1.1-5
+- Commands to run to update image to next redmine release, examples are from 5.0.4 to 5.1.2
 
 ```bash
-sed -i 's/5.1.1-5/5.1.1-5/g' VERSION README.md docker-compose-memcached.yml docker-compose-mysql.yml docker-compose-ssl.yml docker-compose-sqlite3.yml docker-compose-mariadb.yml Dockerfile docker-compose.yml
+sed -i 's/5.1.2/5.1.2/g' VERSION README.md docker-compose-memcached.yml docker-compose-mysql.yml docker-compose-ssl.yml docker-compose-sqlite3.yml docker-compose-mariadb.yml Dockerfile docker-compose.yml
 vim Changelog.md # Update change log
 sudo rm -rf /srv/docker/redmine/ # Clean old run
 docker-compose down
@@ -1011,7 +1011,7 @@ git push origin --tags
 ```
 
 - Open https://github.com/sameersbn/docker-redmine/releases and Draft new release
-- Select tag 5.1.1-5 and set release title to 5.1.1-5
+- Select tag 5.1.2 and set release title to 5.1.2
 - 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 @@
-5.1.1-5
+5.1.2

docker-compose-mariadb.yml

@@ -22,7 +22,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     depends_on:
       - database
     environment:

docker-compose-memcached.yml

@@ -18,7 +18,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     depends_on:
       - postgresql
       - memcached

docker-compose-mysql.yml

@@ -16,7 +16,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     depends_on:
       - mysql
     environment:

docker-compose-sqlite3.yml

@@ -3,7 +3,7 @@ version: '2'
 services:
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     environment:
       - TZ=Asia/Kolkata
 

docker-compose-ssl.yml

@@ -12,7 +12,7 @@ services:
 
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     depends_on:
       - postgresql
     environment:

docker-compose.yml

@@ -17,7 +17,7 @@ services:
       start_period: 10s
   redmine:
     build: ./
-    image: sameersbn/redmine:5.1.1-5
+    image: sameersbn/redmine:5.1.2
     depends_on:
       postgresql:
         condition: service_healthy