Skip to content

Commit 7968790

Browse files
Removed version: from docker-compose examples
1 parent bbcecc0 commit 7968790

File tree

4 files changed

+5
-13
lines changed

4 files changed

+5
-13
lines changed

docs/documentation/devops/code-quality.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ The easiest way to start a Sonarqube® server is to use the [official Sonarqu
1717
For instance you can use the following Docker compose file:
1818

1919
```yaml
20-
version: "3"
21-
2220
services:
2321
sonarqube:
2422
image: sonarqube:community
@@ -34,7 +32,6 @@ services:
3432
- sonarqube_data:/opt/sonarqube/data
3533
- sonarqube_extensions:/opt/sonarqube/extensions
3634
- sonarqube_bundled-plugins:/opt/sonarqube/lib/bundled-plugins
37-
3835
db:
3936
image: postgres:latest
4037
restart: always
@@ -44,7 +41,6 @@ services:
4441
POSTGRES_DB: sonar
4542
volumes:
4643
- postgresql_data:/var/lib/postgresql/data
47-
4844
volumes:
4945
sonarqube_conf:
5046
sonarqube_data:

docs/documentation/operation/auto-setup.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ title: Auto Setup
66
Automated setup
77
================
88

9-
The most classic way of installing an app on an instance is to deploy an empty instance and import modules as the designer user, usually through the UI, the I/O endpoint or using Git pushes/pulls.
9+
The most classic way of installing an app on an instance is to deploy an empty instance and import modules as the designer user, usually through the UI, the I/O endpoint or using Git pushes/pulls.
1010

11-
However, there are many contexts that call for mechanisms to install or update a fully-functionning app without ever having to connect to it.
11+
However, there are many contexts that call for mechanisms to install or update a fully-functionning app without ever having to connect to it.
1212

1313
This document presents two features that aim at accomplishing just that:
1414
- licence packaging
@@ -28,7 +28,7 @@ Alternatively you can pass the content of the license key (in either XML, JSON o
2828
As of version 5.1.6 it is possible to add business modules' ZIP files in the `webapps/ROOT/WEB-INF/modules` folder.
2929
These ZIP files will be imported **if required** at startup following an import specification JSON/YAML file located at the same place.
3030

31-
The import procedure decides whether importing the specified module is required based on the specified version:
31+
The import procedure decides whether importing the specified module is required based on the specified version:
3232
if the module already exists in the database in a version which is higher or equals to the specified version, then no import is done.
3333

3434
The import specification file must be names `<any thing>-importspec.<json|yaml>` and its format is like:
@@ -135,7 +135,6 @@ E.g. 1: Passing `MODULES_IMPORT_SPEC` to a `docker` CLI command line: `-e MODULE
135135
E.g. 2: Setting `MODULES_IMPORT_SPEC` in a `docker-compose.yml` file:
136136

137137
```yaml
138-
version: "3"
139138
services:
140139
simplicite:
141140
image: registry.simplicite.io/platform:<tag>

docs/documentation/operation/docker.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ sudo systemctl enable docker
6969
sudo systemctl start docker
7070
```
7171

72-
> **Note**: by default Docker is allowed to change the firewall rules to open exposed ports.
72+
> **Note**: by default Docker is allowed to change the firewall rules to open exposed ports.
7373
> To disable this behavior you need to edit `/usr/lib/systemd/system/docker.service` cartridge file
7474
> and add `--iptables=false` to the `ExecStart` command.
7575
@@ -587,7 +587,7 @@ and thus the container's `8443` port (exposed here using `-p 8443:8443`) is the
587587
588588
#### Add a custom certificate <span id="addcertificate"></span>
589589
590-
If you need to add a custom certificate (e.g. a CA certificate or a database certificate) to the image you must build a derived image from
590+
If you need to add a custom certificate (e.g. a CA certificate or a database certificate) to the image you must build a derived image from
591591
one of our image using a `Dockerfile` like:
592592
593593
For **CentOS** based-images:
@@ -717,7 +717,6 @@ sudo docker login
717717
Create the following `docker-compose.yml` file:
718718
719719
```yaml
720-
version: "3"
721720
services:
722721
web:
723722
image: registry.simplicite.io/platform:<tag>
@@ -748,7 +747,6 @@ sudo docker-compose up [-d]
748747
> **Note**: if you want to enable SSL you need to add items in the service's ports, environment and volumes sections:
749748
>
750749
> ```yaml
751-
> version: "3"
752750
> services:
753751
> web:
754752
> image: registry.simplicite.io/platform:<tag>

docs/documentation/operation/kubernetes.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,6 @@ For this basic example we will be using the [Kompose tool](https:installation.md
5858
Provided the following Docker compose file `docker-compose.yml`:
5959

6060
```yaml
61-
version: "3"
6261
services:
6362
simplicite:
6463
image: registry.simplicite.io/platform:latest

0 commit comments

Comments
 (0)