Standardize on compose.yaml instead of compose.yml
This commit is contained in:
@@ -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`.
|
||||
|
||||
Reference in New Issue
Block a user