Infra-Mirrors/docker-swag
1
0
Fork 0
mirror of https://github.com/linuxserver/docker-swag.git synced 2024-06-17 10:32:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

update migration info

Browse Source
This commit is contained in:
aptalca 2020-08-21 10:32:00 -04:00
parent dae80a988d
commit 8ddeee5d3d
3 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/greetings.yml vendored
View File

@ -1,6 +1,6 @@
name: Greetings
on: [pull_request, issues]
on: [pull_request_target, issues]
jobs:
greeting:

16
README.md
View File

@ -177,13 +177,15 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
 
## Application Setup
### Migrating from the old `linuxserver/letsencrypt` image
* If using docker cli:
* Stop and remove existing container via `docker stop letsencrypt` and `docker rm letsencrypt`
* Create new container using the sample on this page (container name: `swag`, image name: `linuxserver/swag`)
* If using docker compose:
* Edit the compose yaml to change the image to `linuxserver/swag` and change the service and container names to `swag`
* Issue `docker-compose up -d --remove-orphans`
> ### Migrating from the old `linuxserver/letsencrypt` image
> * If using docker cli:
> * Stop and remove existing container via `docker stop letsencrypt` and `docker rm letsencrypt`
> * Create new container using the sample on this page (container name: `swag`, image name: `linuxserver/swag`)
> * If using docker compose:
> * Edit the compose yaml to change the image to `linuxserver/swag` and change the service and container names to `swag`
> * Issue `docker-compose up -d --remove-orphans`
> Make sure to also update any references to this container by name. For instance, Nextcloud's `config.php` references this container in its `trusted_proxies` directive, which would have to be updated to `swag`.
### Validation and initial setup
* Before running this container, make sure that the url and subdomains are properly forwarded to this container's host, and that port 443 (and/or 80) is not being used by another service on the host (NAS gui, another webserver, etc.).
* For `http` validation, port 80 on the internet side of the router should be forwarded to this container's port 80

16
readme-vars.yml
View File

@ -76,13 +76,15 @@ optional_block_1_items: ""
# application setup block
app_setup_block_enabled: true
app_setup_block: |
### Migrating from the old `linuxserver/letsencrypt` image
* If using docker cli:
* Stop and remove existing container via `docker stop letsencrypt` and `docker rm letsencrypt`
* Create new container using the sample on this page (container name: `swag`, image name: `linuxserver/swag`)
* If using docker compose:
* Edit the compose yaml to change the image to `linuxserver/swag` and change the service and container names to `swag`
* Issue `docker-compose up -d --remove-orphans`
> ### Migrating from the old `linuxserver/letsencrypt` image
> * If using docker cli:
> * Stop and remove existing container via `docker stop letsencrypt` and `docker rm letsencrypt`
> * Create new container using the sample on this page (container name: `swag`, image name: `linuxserver/swag`)
> * If using docker compose:
> * Edit the compose yaml to change the image to `linuxserver/swag` and change the service and container names to `swag`
> * Issue `docker-compose up -d --remove-orphans`
> Make sure to also update any references to this container by name. For instance, Nextcloud's `config.php` references this container in its `trusted_proxies` directive, which would have to be updated to `swag`.
### Validation and initial setup
* Before running this container, make sure that the url and subdomains are properly forwarded to this container's host, and that port 443 (and/or 80) is not being used by another service on the host (NAS gui, another webserver, etc.).
* For `http` validation, port 80 on the internet side of the router should be forwarded to this container's port 80