Run update.sh

This commit is contained in:
Docker Library Bot 2020-04-07 18:11:10 +00:00
parent 026e47e91a
commit 42f7128f9a
2 changed files with 12 additions and 12 deletions

View File

@ -265,9 +265,9 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```console
cd bonita_migration
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.49.0.zip
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.50.0.zip
wget https://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
unzip bonita-migration-distrib-2.49.0.zip
unzip bonita-migration-distrib-2.50.0.zip
unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
```
@ -282,14 +282,14 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```console
cd bonita_migration
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.49.0.zip
unzip bonita-migration-distrib-2.49.0.zip
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.50.0.zip
unzip bonita-migration-distrib-2.50.0.zip
```
- Configure the migration tool
```console
$ cd bonita-migration-distrib-2.49.0
$ cd bonita-migration-distrib-2.50.0
```
edit the migration tool config to point towards the copy of bonita home and db
@ -326,17 +326,17 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
- If >= 7.3.0
```console
$ docker run --name=bonita_7.10.3_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 bonita:7.10.3
$ docker run --name=bonita_7.10.4_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 bonita:7.10.4
```
- Reapply specific configuration if needed, for example with a version >= 7.3.0 :
```console
$ docker exec -ti bonita_7.10.3_postgres /bin/bash
$ docker exec -ti bonita_7.10.4_postgres /bin/bash
```
```console
$ cd /opt/bonita/BonitaCommunity-7.10.3/setup
$ cd /opt/bonita/BonitaCommunity-7.10.4/setup
$ ./setup.sh pull
$ TENANT_LOGIN=tech_user
$ TENANT_PASSWORD=secret
@ -356,7 +356,7 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```
```console
$ docker restart bonita_7.10.3_postgres
$ docker restart bonita_7.10.4_postgres
```
- Specific consideration regarding migration to Java 11 in Bonita 7.9
@ -480,7 +480,7 @@ For example, you can increase the log level :
```console
$ mkdir -p custom_bonita
$ echo '#!/bin/bash' > custom_bonita/bonita.sh
$ echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.10.3/server/conf/logging.properties' >> custom_bonita/bonita.sh
$ echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.10.4/server/conf/logging.properties' >> custom_bonita/bonita.sh
$ chmod +x custom_bonita/bonita.sh
$ docker run --name bonita_custom -v "$PWD"/custom_bonita/:/opt/custom-init.d -d -p 8080:8080 bonita
@ -498,7 +498,7 @@ Note: There are several ways to check the `bonita` logs. Till Bonita 7.8, one of
```console
$ docker exec -ti bonita_custom /bin/bash
tail -f /opt/bonita/BonitaCommunity-7.10.3/server/logs/bonita.`date +%Y-%m-%d`.log
tail -f /opt/bonita/BonitaCommunity-7.10.4/server/logs/bonita.`date +%Y-%m-%d`.log
```
Since Bonita 7.9 bonita logs are redirected towards standard output and directly accessible using

View File

@ -72,7 +72,7 @@ If you'd like to be able to access the instance from the host without the contai
$ docker run -d --name some-ghost -e url=http://localhost:3001 -p 3001:2368 ghost
```
Then, access it via `http://localhost:3001` or `http://host-ip:3001` in a browser.
If all goes well, you'll be able to access your new site on `http://localhost:3001` and `http://localhost:3001/ghost` to access Ghost Admin (or `http://host-ip:3001` and `http://host-ip:3001/ghost`, respectively).
### Upgrading Ghost