multi-process docker image: advice the usage of volumes/linked database container
Dominik Sander
1 changed files with 8 additions and 2 deletions
+ 8
- 2
docker/multi-process/README.md
@@ -23,7 +23,9 @@ and |
||
| 23 | 23 |
Its recommended to use an image that allows you to create a database via environmental variables at docker run, like `paintedfox / postgresql` or `centurylink / mysql`, so the db is populated when this script runs. |
| 24 | 24 |
|
| 25 | 25 |
If you do not link a database container, a built-in mysql database will be started. |
| 26 |
-There is an exported docker volume of /var/lib/mysql to allow persistence of that mysql database. |
|
| 26 |
+There is an exported docker volume of `/var/lib/mysql` to allow persistence of that mysql database. |
|
| 27 |
+ |
|
| 28 |
+__NOTE:__ If you do not export the volme, or use a linked database container, you cannot update Huginn without losing your data. |
|
| 27 | 29 |
|
| 28 | 30 |
Additionally, the database variables may be overridden from the above as per the standard Huginn documentation: |
| 29 | 31 |
|
@@ -45,10 +47,14 @@ The CMD launches Huginn via the scripts/init script. This may become the ENTRYPO |
||
| 45 | 47 |
|
| 46 | 48 |
## Usage |
| 47 | 49 |
|
| 48 |
-Simple stand-alone usage: |
|
| 50 |
+Simple stand-alone usage (use only for testing/evaluation as it can not be updated without losing data): |
|
| 49 | 51 |
|
| 50 | 52 |
docker run -it -p 3000:3000 cantino/huginn |
| 51 | 53 |
|
| 54 |
+Use a volume to export the data of the internal mysql server: |
|
| 55 |
+ |
|
| 56 |
+ docker run -it -p 3000:3000 -v /home/huginn/mysql-data:/var/lib/mysql cantino/huginn |
|
| 57 |
+ |
|
| 52 | 58 |
To link to another mysql container, for example: |
| 53 | 59 |
|
| 54 | 60 |
docker run --rm --name huginn_mysql \ |