Standardize on compose.yaml instead of compose.yml
This commit is contained in:
@@ -65,7 +65,7 @@ tree:
|
||||
- srv:
|
||||
- docker:
|
||||
- dockge:
|
||||
- compose.yml
|
||||
- compose.yaml
|
||||
---
|
||||
::
|
||||
|
||||
@@ -81,7 +81,7 @@ sudo mkdir dockge
|
||||
|
||||
```bash [Terminal]
|
||||
cd /srv/docker/dockge
|
||||
sudo nano compose.yml
|
||||
sudo nano compose.yaml
|
||||
```
|
||||
Paste the following:
|
||||
|
||||
@@ -122,7 +122,7 @@ More info on [Dockge and how to use it](https://github.com/louislam/dockge)
|
||||
And there you go! Docker and a tool to easily manage your containers are ready!
|
||||
|
||||
## [Watchtower](https://watchtower.nickfedor.com/), to auto-update containers
|
||||
Watchtower is a container that checks for updates and pulls new images automatically, just by adding a label in your containers’ `compose.yml` files.
|
||||
Watchtower is a container that checks for updates and pulls new images automatically, just by adding a label in your containers’ `compose.yaml` files.
|
||||
|
||||
### Configuration
|
||||
|
||||
@@ -178,7 +178,7 @@ WH_URL=
|
||||
|
||||
#### Enable Watchtower on other containers
|
||||
|
||||
To have Watchtower monitor your other containers, add this to their `compose.yml`:
|
||||
To have Watchtower monitor your other containers, add this to their `compose.yaml`:
|
||||
|
||||
```yaml [compose.yaml]
|
||||
---
|
||||
|
||||
@@ -42,7 +42,7 @@ tree:
|
||||
- nginx.conf
|
||||
- proxy-confs:
|
||||
- dockge.subdomain.conf
|
||||
- compose.yml
|
||||
- compose.yaml
|
||||
- .env
|
||||
---
|
||||
::
|
||||
@@ -348,7 +348,7 @@ Save and exit. The configuration will update within a few seconds.
|
||||
|
||||
::note
|
||||
|
||||
By default, SWAG doesn’t recognize the name "dockge". You’ll need to add Dockge’s network to SWAG’s `compose.yml`.
|
||||
By default, SWAG doesn’t recognize the name "dockge". You’ll need to add Dockge’s network to SWAG’s `compose.yaml`.
|
||||
::
|
||||
|
||||
### Add Dockge's network to SWAG
|
||||
@@ -398,7 +398,7 @@ sudo cp servicename.subdomain.conf.sample servicename.subdomain.conf
|
||||
|
||||
__If the subdomain is not redirected properly__
|
||||
- Open the file and verify the container name in `set $upstream_app containername;`{lang=nginx}
|
||||
- Make sure you added the container's network in SWAG’s `compose.yml`
|
||||
- Make sure you added the container's network in SWAG’s `compose.yaml`
|
||||
::
|
||||
|
||||
You can also customize the subdomain by editing `server_name yoursubdomain.*;`{lang=nginx} and renaming the file to `yoursubdomain.subdomain.conf`.
|
||||
|
||||
@@ -165,7 +165,7 @@ Save and exit. The configuration will update in a few seconds.
|
||||
|
||||
::note
|
||||
|
||||
By default, SWAG doesn’t know the name "speedtest-tracker". To allow access, you need to add Speedtest Tracker’s network to SWAG’s `compose.yml`.
|
||||
By default, SWAG doesn’t know the name "speedtest-tracker". To allow access, you need to add Speedtest Tracker’s network to SWAG’s `compose.yaml`.
|
||||
::
|
||||
|
||||
Go to Dockge, and edit SWAG’s compose to include Speedtest Tracker’s network:
|
||||
|
||||
Reference in New Issue
Block a user