Use consistent docker-compose file version in docs

This commit is contained in:
Jamie Curnow 2023-03-22 09:41:19 +10:00
parent 8fdb8ac853
commit 79fedfcea4
No known key found for this signature in database
GPG Key ID: FFBB624C43388E9E
3 changed files with 8 additions and 7 deletions

View File

@ -56,7 +56,7 @@ I won't go in to too much detail here but here are the basics for someone new to
2. Create a docker-compose.yml file similar to this:
```yml
version: '3'
version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'

View File

@ -25,7 +25,7 @@ networks:
Let's look at a Portainer example:
```yml
version: '3'
version: '3.8'
services:
portainer:
@ -60,14 +60,14 @@ healthcheck:
timeout: 3s
```
## Docker Secrets
## Docker File Secrets
This image supports the use of Docker secrets to import from file and keep sensitive usernames or passwords from being passed or preserved in plaintext.
This image supports the use of Docker secrets to import from files and keep sensitive usernames or passwords from being passed or preserved in plaintext.
You can set any environment variable from a file by appending `__FILE` (double-underscore FILE) to the environmental variable name.
```yml
version: "3.7"
version: '3.8'
secrets:
# Secrets are single-line text files where the sole content is the secret
@ -106,6 +106,7 @@ services:
- MYSQL_PWD
depends_on:
- db
db:
image: jc21/mariadb-aria
restart: unless-stopped

View File

@ -5,7 +5,7 @@
Create a `docker-compose.yml` file:
```yml
version: "3"
version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
@ -51,7 +51,7 @@ are going to use.
Here is an example of what your `docker-compose.yml` will look like when using a MariaDB container:
```yml
version: "3"
version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'