Browse Source

Run update.sh

Docker Library Bot 6 years ago
parent
commit
dea4657d2e
6 changed files with 34 additions and 24 deletions
  1. 19 13
      bonita/README.md
  2. 6 4
      convertigo/README.md
  3. 1 1
      eclipse-mosquitto/README.md
  4. 5 3
      maven/README.md
  5. 1 1
      opensuse/README.md
  6. 2 2
      ros/README.md

+ 19 - 13
bonita/README.md

@@ -75,10 +75,12 @@ PostgreSQL is the recommanded database.
 
 [Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.8/database-configuration#toc5):
 
-	mkdir -p custom_postgres
-	echo '#!/bin/bash' > custom_postgres/bonita.sh
-	echo 'sed -i "s/^.*max_prepared_transactions\s*=\s*\(.*\)$/max_prepared_transactions = 100/" "$PGDATA"/postgresql.conf' >> custom_postgres/bonita.sh
-	chmod +x custom_postgres/bonita.sh
+```console
+$ mkdir -p custom_postgres
+$ echo '#!/bin/bash' > custom_postgres/bonita.sh
+$ echo 'sed -i "s/^.*max_prepared_transactions\s*=\s*\(.*\)$/max_prepared_transactions = 100/" "$PGDATA"/postgresql.conf' >> custom_postgres/bonita.sh
+$ chmod +x custom_postgres/bonita.sh
+```
 
 Mount that directory location as /docker-entrypoint-initdb.d inside the PostgreSQL container:
 
@@ -98,9 +100,11 @@ There are known issues with the management of XA transactions by MySQL engine an
 
 [Increase the packet size](https://documentation.bonitasoft.com/bonita/7.8/database-configuration#toc5) which is set by default to 1M:
 
-	mkdir -p custom_mysql
-	echo "[mysqld]" > custom_mysql/bonita.cnf
-	echo "max_allowed_packet=16M" >> custom_mysql/bonita.cnf
+```console
+$ mkdir -p custom_mysql
+$ echo "[mysqld]" > custom_mysql/bonita.cnf
+$ echo "max_allowed_packet=16M" >> custom_mysql/bonita.cnf
+```
 
 Mount that directory location as /etc/mysql/conf.d inside the MySQL container:
 
@@ -452,12 +456,14 @@ If you would like to do additional initialization, you can add a `*.sh` script u
 
 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/BonitaCommunity-7.8.1-Tomcat-8.5.34/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
+```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.8.1-Tomcat-8.5.34/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
+```
 
 Note: There are several ways to check the `bonita` logs. One of them is
 

+ 6 - 4
convertigo/README.md

@@ -159,10 +159,12 @@ $ docker run -d --name C8O-MBAAS -e JAVA_OPTS="-Xmx4096m -DjvmRoute=server1" -p
 
 You can use this [stack](https://github.com/convertigo/docker/blob/master/compose/mbaas/docker-compose.yml) to run a complete Convertigo MBaaS server with FullSync repository and MySQL analytics in a few command lines.
 
-	mkdir c8oMBaaS
-	cd c8oMBaaS
-	wget https://raw.githubusercontent.com/convertigo/docker/master/compose/mbaas/docker-compose.yml
-	docker-compose up -d
+```console
+$ mkdir c8oMBaaS
+$ cd c8oMBaaS
+$ wget https://raw.githubusercontent.com/convertigo/docker/master/compose/mbaas/docker-compose.yml
+$ docker-compose up -d
+```
 
 # Image Variants
 

+ 1 - 1
eclipse-mosquitto/README.md

@@ -16,7 +16,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`1.5.5`, `1.5`, `latest` (*docker/1.5/Dockerfile*)](https://github.com/eclipse/mosquitto/blob/a0a37d385db4421d7151f1fe969a7b00d4516c24/docker/1.5/Dockerfile)
+-	[`1.5.6`, `1.5`, `latest` (*docker/1.5/Dockerfile*)](https://github.com/eclipse/mosquitto/blob/ff36baa49e37eb27d998314d46f01ddd914fdd65/docker/1.5/Dockerfile)
 
 # Quick reference
 

+ 5 - 3
maven/README.md

@@ -86,9 +86,11 @@ $ docker build --tag my_local_maven:3.5.2-jdk-8 .
 
 The local Maven repository can be reused across containers by creating a volume and mounting it in `/root/.m2`.
 
-	docker volume create --name maven-repo
-	docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will download artifacts
-	docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will reuse downloaded artifacts
+```console
+$ docker volume create --name maven-repo
+$ docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will download artifacts
+$ docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will reuse downloaded artifacts
+```
 
 Or you can just use your home .m2 cache directory that you share e.g. with your Eclipse/IDEA:
 

+ 1 - 1
opensuse/README.md

@@ -18,7 +18,7 @@ WARNING:
 
 This image has been deprecated in favor of the [`opensuse/leap`](https://hub.docker.com/r/opensuse/leap) and [`opensuse/tumbleweed`](https://hub.docker.com/r/opensuse/tumbleweed) images provided and maintained by the [openSUSE Project](https://www.opensuse.org/) release team.
 
-`opensuse:42.3` (= `opensuse:latest`) will receive security relevant fixes until the [EOL of Leap 42.3](https://en.opensuse.org/Lifetime#openSUSE_Leap). Newer openSUSE Leap releases such as 15.x are only available at [`opensuse/leap`](https://hub.docker.com/r/opensuse/leap)\.
+`opensuse:42.3` (= `opensuse:latest`) will receive security relevant fixes until the [EOL of Leap 42.3](https://en.opensuse.org/Lifetime#openSUSE_Leap). Newer openSUSE Leap releases such as 15.x are only available at [`opensuse/leap`](https://hub.docker.com/r/opensuse/leap).
 
 The opensuse:tumbleweed image is no longer updated, please use [`opensuse/tumbleweed`](https://hub.docker.com/r/opensuse/tumbleweed) instead. [`opensuse/tumbleweed`](https://hub.docker.com/r/opensuse/tumbleweed) is updated on every snapshot release.
 

+ 2 - 2
ros/README.md

@@ -253,7 +253,7 @@ $ docker rm master talker listener
 
 ### Compose
 
-Now that you have an appreciation for bootstrapping a distributed ROS example manually, lets try and automate it using [`docker-compose`](https://docs.docker.com/compose/)\.
+Now that you have an appreciation for bootstrapping a distributed ROS example manually, lets try and automate it using [`docker-compose`](https://docs.docker.com/compose/).
 
 > Start by making a folder named `rostutorials` and moving the Dockerfile we used earlier inside this directory. Then create a yaml file named `docker-compose.yml` in the same directory and paste the following inside:
 
@@ -308,7 +308,7 @@ $ docker-compose stop
 $ docker-compose rm
 ```
 
-> Note: the auto-generated network, `rostutorials_default`, will persist over the life of the docker engine or until you explicitly remove it using [`docker network rm`](https://docs.docker.com/engine/reference/commandline/network_rm/)\.
+> Note: the auto-generated network, `rostutorials_default`, will persist over the life of the docker engine or until you explicitly remove it using [`docker network rm`](https://docs.docker.com/engine/reference/commandline/network_rm/).
 
 # More Resources