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
Copy file name to clipboardExpand all lines: README.md
+1-62Lines changed: 1 addition & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,20 +207,6 @@ Redmine uses a database backend to store its data.
207
207
208
208
The internal mysql server has been removed from the image. Please use a linked [mysql](#linking-to-mysql-container) or [postgresql](#linking-to-postgresql-container) container instead or connect with an external [mysql](#external-mysql-server) or [postgresql](#external-postgresql-server) server.
209
209
210
-
If you have been using the internal mysql server follow these instructions to migrate to a linked mysql container:
211
-
212
-
Assuming that your mysql data is available at `/srv/docker/redmine/mysql`
This will start a mysql container with your existing mysql data. Now login to the mysql container and create a user for the existing `redmine_production` database.
221
-
222
-
All you need to do now is link this mysql container to the redmine container using the `--link=mysql-redmine:mysql` option and provide the `DB_NAME`, `DB_USER` and `DB_PASS` parameters.
223
-
224
210
Refer to [Linking to MySQL Container](#linking-to-mysql-container) for more information.
225
211
226
212
#### External MySQL Server
@@ -252,54 +238,7 @@ This will initialize the redmine database and after a couple of minutes your red
252
238
253
239
#### Linking to MySQL Container
254
240
255
-
You can link this image with a mysql container for the database requirements. The alias of the mysql server container should be set to **mysql** while linking with the redmine image.
256
-
257
-
If a mysql container is linked, only the `DB_ADAPTER`, `DB_HOST` and `DB_PORT` settings are automatically retrieved using the linkage. You may still need to set other database connection parameters such as the `DB_NAME`, `DB_USER`, `DB_PASS` and so on.
258
-
259
-
To illustrate linking with a mysql container, we will use the [sameersbn/mysql](https://github.com/sameersbn/docker-mysql) image. When using docker-mysql in production you should mount a volume for the mysql data store. Please refer the [README](https://github.com/sameersbn/docker-mysql/blob/master/README.md) of docker-mysql for details.
260
-
261
-
First, lets pull the mysql image from the docker index.
262
-
263
-
```bash
264
-
docker pull sameersbn/mysql:5.7.22-1
265
-
```
266
-
267
-
For data persistence lets create a store for the mysql and start the container.
268
-
269
-
SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.
The above command will create a database named `redmine_production` and also create a user named `redmine` with the password `password` with full/remote access to the `redmine_production` database.
287
-
288
-
We are now ready to start the redmine application.
289
-
290
-
```bash
291
-
docker run --name=redmine -it --rm --link=mysql-redmine:mysql \
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:
0 commit comments