Run update.sh
This commit is contained in:
Docker Library Bot
parent
7639639dbb
commit
3abc77fef3
|
|
@ -16,8 +16,8 @@ WARNING:
|
|||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`3.13.0.1`, `latest` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/325c0b8a906823e7ad3afd543d4fe13789ef5664/Dockerfile)
|
||||
- [`3.12.1.1` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/03fe0e974b0866334e06a4655c17928ad2d5dbb0/Dockerfile)
|
||||
- [`3.13.0.1` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/325c0b8a906823e7ad3afd543d4fe13789ef5664/Dockerfile)
|
||||
- [`3.14.0`, `latest` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/01158e0954d503f9c845fdc379fff7fc58828c48/Dockerfile)
|
||||
|
||||
# Quick reference
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ WARNING:
|
|||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`7.4.3` (*7.4/Dockerfile*)](https://github.com/Bonitasoft-Community/docker_bonita/blob/5e4d4c6d86a90b2f7639215e4098097200a8751a/7.4/Dockerfile)
|
||||
- [`7.5.0`, `latest` (*7.5/Dockerfile*)](https://github.com/Bonitasoft-Community/docker_bonita/blob/d5b521cca0d88eab6f093ef38045d456ebbecde4/7.5/Dockerfile)
|
||||
- [`7.5.1`, `latest` (*7.5/Dockerfile*)](https://github.com/Bonitasoft-Community/docker_bonita/blob/f2f0c810162d12091ebab5cf29340fb800102cf5/7.5/Dockerfile)
|
||||
|
||||
# Quick reference
|
||||
|
||||
|
|
@ -205,9 +205,9 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
|
|||
|
||||
```console
|
||||
cd bonita_migration
|
||||
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.22.0.zip
|
||||
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.23.0.zip
|
||||
wget http://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
|
||||
unzip bonita-migration-distrib-2.22.0.zip
|
||||
unzip bonita-migration-distrib-2.23.0.zip
|
||||
unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
|
||||
```
|
||||
|
||||
|
|
@ -222,13 +222,13 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
|
|||
|
||||
```console
|
||||
cd bonita_migration
|
||||
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.22.0.zip
|
||||
unzip bonita-migration-distrib-2.22.0.zip
|
||||
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.23.0.zip
|
||||
unzip bonita-migration-distrib-2.23.0.zip
|
||||
```
|
||||
|
||||
- Configure the migration tool
|
||||
|
||||
cd bonita-migration-distrib-2.22.0
|
||||
cd bonita-migration-distrib-2.23.0
|
||||
|
||||
edit the migration tool config to point towards the copy of bonita home and db
|
||||
|
||||
|
|
@ -260,17 +260,17 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
|
|||
- If >= 7.3.0
|
||||
|
||||
```console
|
||||
$ docker run --name=bonita_7.5.0_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 bonita:7.5.0
|
||||
$ docker run --name=bonita_7.5.1_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 bonita:7.5.1
|
||||
```
|
||||
|
||||
- Reapply specific configuration if needed, for example with a version >= 7.3.0 :
|
||||
|
||||
```console
|
||||
$ docker exec -ti bonita_7.5.0_postgres /bin/bash
|
||||
$ docker exec -ti bonita_7.5.1_postgres /bin/bash
|
||||
```
|
||||
|
||||
```console
|
||||
$ cd /opt/bonita/BonitaBPMCommunity-7.5.0-Tomcat-7.0.76/setup
|
||||
$ cd /opt/bonita/BonitaBPMCommunity-7.5.1-Tomcat-7.0.76/setup
|
||||
$ ./setup.sh pull
|
||||
$ TENANT_LOGIN=tech_user
|
||||
$ TENANT_PASSWORD=secret
|
||||
|
|
@ -290,7 +290,7 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
|
|||
```
|
||||
|
||||
```console
|
||||
$ docker restart bonita_7.5.0_postgres
|
||||
$ docker restart bonita_7.5.1_postgres
|
||||
```
|
||||
|
||||
For more details regarding Bonita migration, see the [documentation](http://documentation.bonitasoft.com/?page=migrate-from-an-earlier-version-of-bonita-bpm).
|
||||
|
|
@ -393,7 +393,7 @@ For example, you can increase the log level :
|
|||
|
||||
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/BonitaBPMCommunity-7.5.0-Tomcat-7.0.76/server/conf/logging.properties' >> custom_bonita/bonita.sh
|
||||
echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaBPMCommunity-7.5.1-Tomcat-7.0.76/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
|
||||
|
|
@ -402,7 +402,7 @@ Note: There are several ways to check the `bonita` logs. One of them is
|
|||
|
||||
```console
|
||||
$ docker exec -ti bonita_custom /bin/bash
|
||||
tail -f /opt/bonita/BonitaBPMCommunity-7.5.0-Tomcat-7.0.76/server/logs/bonita.`date +%Y-%m-%d`.log
|
||||
tail -f /opt/bonita/BonitaBPMCommunity-7.5.1-Tomcat-7.0.76/server/logs/bonita.`date +%Y-%m-%d`.log
|
||||
```
|
||||
|
||||
# License
|
||||
|
|
|
|||
|
|
@ -71,10 +71,10 @@ The second option is a `fpm` container. It is based on the [php-fpm](https://hub
|
|||
The apache image contains a webserver and exposes port 80. To start the container type:
|
||||
|
||||
```console
|
||||
$ docker run -d nextcloud
|
||||
$ docker run -d -p 8080:80 nextcloud
|
||||
```
|
||||
|
||||
Now you can access Nextcloud at http://localhost/ from your host system.
|
||||
Now you can access Nextcloud at http://localhost:8080/ from your host system.
|
||||
|
||||
## Using the fpm image
|
||||
|
||||
|
|
@ -165,6 +165,8 @@ services:
|
|||
|
||||
app:
|
||||
image: nextcloud
|
||||
ports:
|
||||
- 8080:80
|
||||
links:
|
||||
- db
|
||||
volumes:
|
||||
|
|
@ -173,6 +175,8 @@ services:
|
|||
|
||||
```
|
||||
|
||||
Then run `docker-compose up -d`, now you can access Nextcloud at http://localhost:8080/ from your host system.
|
||||
|
||||
## Base version - FPM
|
||||
|
||||
When using the FPM image you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combindes with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also need access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the `volumes_from` option.The configuration for nginx is stored in the configuration file `nginx.conf`, that is mounted into the container. An example can be found in the examples section [here](https://github.com/nextcloud/docker/tree/master/.examples).
|
||||
|
|
@ -210,6 +214,8 @@ services:
|
|||
|
||||
web:
|
||||
image: nginx
|
||||
ports:
|
||||
- 8080:80
|
||||
links:
|
||||
- app
|
||||
volumes:
|
||||
|
|
@ -219,6 +225,8 @@ services:
|
|||
restart: always
|
||||
```
|
||||
|
||||
Then run `docker-compose up -d`, now you can access Nextcloud at http://localhost:8080/ from your host system.
|
||||
|
||||
# Make your Nextcloud available from the internet
|
||||
|
||||
Until here your Nextcloud is just available from you docker host. If you want you Nextcloud available from the internet adding SSL encryption is mandatory.
|
||||
|
|
@ -231,32 +239,6 @@ We recommend using a reverse proxy in front of our Nextcloud installation. Your
|
|||
|
||||
In our [examples](https://github.com/nextcloud/docker/tree/master/.examples) section we have an example for a fully automated setup using a reverse proxy, a container for [Let's Encrypt](https://letsencrypt.org/) certificate handling, database and Nextcloud. It uses the popular [nginx-proxy](https://github.com/jwilder/nginx-proxy) and [docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion) containers. Please check the according documentations before using this setup.
|
||||
|
||||
## HTTP - insecure, just for development / debugging / testing
|
||||
|
||||
When you're testing you can use this image without the ssl encryption. **Never use this method on a Nextcloud install where actual user data is stored!**
|
||||
|
||||
You just have to map the webserver port to your host. For the apache image add `-p 80:80` to your docker run command or add to your compose file:
|
||||
|
||||
```diff
|
||||
...
|
||||
app:
|
||||
image: nextcloud
|
||||
+ ports:
|
||||
+ - 80:80
|
||||
...
|
||||
```
|
||||
|
||||
For the fpm image you need a webserver in front. If you're following the docker-compose example above, add:
|
||||
|
||||
```diff
|
||||
...
|
||||
web:
|
||||
image: nginx
|
||||
+ ports:
|
||||
+ - 80:80
|
||||
...
|
||||
```
|
||||
|
||||
# First use
|
||||
|
||||
When you first access your Nextcloud, the setup wizard will appear and ask you to choose an administrator account, password and the database connection. For the database use `db` as host and `nextcloud` as table and user name. Also enter the password you chose in your `docker-compose.yml` file.
|
||||
|
|
|
|||
|
|
@ -92,12 +92,12 @@ Running Redmine with a database server is the recommened way.
|
|||
$ docker run -d --name some-redmine --link some-postgres:postgres redmine
|
||||
```
|
||||
|
||||
## ... via [`docker-compose`](https://github.com/docker/compose)
|
||||
## ... via [`docker stack deploy`](https://docs.docker.com/engine/reference/commandline/stack_deploy/) or [`docker-compose`](https://github.com/docker/compose)
|
||||
|
||||
Example `docker-compose.yml` for `redmine`:
|
||||
Example `stack.yml` for `redmine`:
|
||||
|
||||
```yaml
|
||||
version: '2'
|
||||
version: '3.1'
|
||||
|
||||
services:
|
||||
|
||||
|
|
@ -108,19 +108,17 @@ services:
|
|||
environment:
|
||||
REDMINE_DB_MYSQL: db
|
||||
REDMINE_DB_PASSWORD: example
|
||||
depends_on:
|
||||
- db
|
||||
restart: always
|
||||
|
||||
db:
|
||||
image: mariadb
|
||||
image: mysql:5.7
|
||||
environment:
|
||||
MYSQL_ROOT_PASSWORD: example
|
||||
MYSQL_DATABASE: redmine
|
||||
restart: always
|
||||
```
|
||||
|
||||
Run `docker-compose up`, wait for it to initialize completely, and visit `http://localhost:8080` or `http://host-ip:8080`.
|
||||
[](http://play-with-docker.com?stack=https://raw.githubusercontent.com/docker-library/docs/9cb58e0970fb4cad06a7787418ceb3e39ca1b853/redmine/stack.yml)
|
||||
|
||||
Run `docker stack deploy -c stack.yml redmine` (or `docker-compose -f stack.yml up`), wait for it to initialize completely, and visit `http://swarm-ip:8080`, `http://localhost:8080`, or `http://host-ip:8080` (as appropriate).
|
||||
|
||||
## Alternative Web Server
|
||||
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ services:
|
|||
|
||||
[](http://play-with-docker.com?stack=https://raw.githubusercontent.com/docker-library/docs/0cb43ce8ad1da073bbc30c6245cdffb433ba51ba/wordpress/stack.yml)
|
||||
|
||||
Run `docker stack deploy -c stack.yml wordpress` (or `docker-compose -f stack.yml up`), wait for it to initialize completely, and visit `http://swarm-ip:8080`, `http://localhost:8080` or `http://host-ip:8080` (as appropriate).
|
||||
Run `docker stack deploy -c stack.yml wordpress` (or `docker-compose -f stack.yml up`), wait for it to initialize completely, and visit `http://swarm-ip:8080`, `http://localhost:8080`, or `http://host-ip:8080` (as appropriate).
|
||||
|
||||
## Adding additional libraries / extensions
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue