Fix compose network snippet indentation across app articles

This commit is contained in:
Djeex
2026-09-07 13:09:23 +02:00
parent 3c85fec634
commit 6a27518be1
44 changed files with 104 additions and 104 deletions
@@ -152,9 +152,9 @@ Go to Dockge and edit SWAG's compose file by adding TinyAuth's network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Attach container to custom network
networks: # Attach container to custom network
# ...
- tinyauth # Name of the declared network
@@ -131,9 +131,9 @@ Go to Dockge and edit SWAG's compose file by adding Pocket ID's network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Attach container to custom network
networks: # Attach container to custom network
# ...
- pocket-id # Name of the declared network
@@ -153,9 +153,9 @@ In Dockge, edit the SWAG compose and add the Uptime-Kuma network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Link container to custom network
networks: # Link container to custom network
# ...
- uptime-kuma # Name of the declared network
@@ -97,9 +97,9 @@ Go to Dockge and edit the SWAG compose file to add Dozzles network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to a custom network
networks: # Connects the container to a custom network
# ...
- dozzle # Network name declared in the stack
@@ -167,9 +167,9 @@ In Dockge, edit Swag's compose file and add Beszels network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks:
networks:
# ...
- beszel # network declared in the stack
@@ -109,9 +109,9 @@ Go to Dockge, and edit the SWAG compose by adding the UpSnap network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to the custom network
networks: # Connects the container to the custom network
# ...
- upsnap # Network name declared in the stack
+3 -3
View File
@@ -26,7 +26,7 @@ tree:
- srv:
- docker:
- jellyfin:
- compose.yml
- compose.yaml
- .env
- config/
- sonarr:
@@ -406,9 +406,9 @@ Go to Dockge, edit the SWAG compose file, and add the Seerr network, which is th
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to a custom network
networks: # Connects the container to a custom network
# ...
- jellyfin # Name of the network declared in the stack
+2 -2
View File
@@ -71,9 +71,9 @@ In Dockge, open the SWAG stack and edit the compose file to add Immich's network
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to the custom network
networks: # Connects the container to the custom network
# ...
- immich # Network name defined in the stack
+2 -2
View File
@@ -101,9 +101,9 @@ In Dockge, go to your SWAG stack and edit the compose to add Nextcloud's network
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks:
networks:
# ...
- nextcloud
@@ -127,9 +127,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add File Browser Qu
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to the custom network
networks: # Connects the container to the custom network
# ...
- filebrowser-quantum # Name of the network declared in the stack
+2 -2
View File
@@ -91,9 +91,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add the pingvin net
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to the custom network
networks: # Connects the container to the custom network
# ...
- pingvin # Name of the network declared in the stack
@@ -135,9 +135,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add code-servers
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to a custom network
networks: # Connects the container to a custom network
# ...
- code-server # Name of the network defined in the stack
@@ -90,9 +90,9 @@ In Dockge, go to the SWAG stack and edit the compose file by adding Forgejo's ne
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connect the container to the custom network
networks: # Connect the container to the custom network
# ...
- forgejo # Name of the declared network
@@ -68,9 +68,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add the IT Tools ne
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects the container to the custom network
networks: # Connects the container to the custom network
# ...
- it-tools # Network name as defined in the IT Tools stack
+2 -2
View File
@@ -126,9 +126,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add the AdGuard net
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connect the container to the custom network
networks: # Connect the container to the custom network
# ...
- adguard # Name of the network declared in the stack
+2 -2
View File
@@ -124,9 +124,9 @@ In Dockge, go to the SWAG stack and edit the compose file to add the Vaultwarden
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Connects container to custom network
networks: # Connects container to custom network
# ...
- vaultwarden # Name of the declared network
@@ -43,7 +43,7 @@ tree:
- docker:
- authentik:
- .env
- compose.yml
- compose.yaml
- media/
- certs/
- custom-template/
@@ -69,9 +69,9 @@ echo "AUTHENTIK_SECRET_KEY=$(openssl rand 60 | base64)" | sudo tee -a .env
::note
To generate the keys, we created the folders ahead of deployment using Dockge. Dockge will prevent you from creating a stack with the same name in these folders unless a `compose.yml` file exists. So, create an empty `compose.yml` so it appears as an inactive stack:
To generate the keys, we created the folders ahead of deployment using Dockge. Dockge will prevent you from creating a stack with the same name in these folders unless a `compose.yaml` file exists. So, create an empty `compose.yaml` so it appears as an inactive stack:
```bash [Terminal]
sudo nano /srv/docker/authentik/compose.yml
sudo nano /srv/docker/authentik/compose.yaml
```
::
@@ -284,9 +284,9 @@ Go to Dockge, and edit the SWAG compose file to add the Authentik network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Attach the container to the custom network
networks: # Attach the container to the custom network
# ...
- authentik # Name of the network declared in the stack
@@ -493,9 +493,9 @@ sudo nano /srv/docker/swag/compose.yaml
---
services:
swag:
container_name: #...
container_name: #...
# ...
networks: # Attach the container to the custom network
networks: # Attach the container to the custom network
- authentik-outpost # Network name as declared in the stack
+2 -2
View File
@@ -172,9 +172,9 @@ Go to Dockge and edit SWAG's compose file by adding Arcane's network:
---
services:
swag:
container_name: # ...
container_name: # ...
# ...
networks: # Attach container to custom network
networks: # Attach container to custom network
# ...
- arcane # Name of the declared network