mirror of
https://github.com/linuxserver/docker-swag.git
synced 2026-03-03 00:43:34 +09:00
Compare commits
11 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
055801b05b | ||
|
|
16f4b226a3 | ||
|
|
91497c3479 | ||
|
|
a7b3cab778 | ||
|
|
203451a696 | ||
|
|
5727a9260c | ||
|
|
aee7dcf14a | ||
|
|
5080db685b | ||
|
|
8ddeee5d3d | ||
|
|
dae80a988d | ||
|
|
82ab2597b9 |
2
.github/workflows/greetings.yml
vendored
2
.github/workflows/greetings.yml
vendored
@@ -1,6 +1,6 @@
|
||||
name: Greetings
|
||||
|
||||
on: [pull_request, issues]
|
||||
on: [pull_request_target, issues]
|
||||
|
||||
jobs:
|
||||
greeting:
|
||||
|
||||
19
README.md
19
README.md
@@ -35,7 +35,7 @@ Find us at:
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-swag/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/swag/latest/index.html)
|
||||
|
||||
SWAG - Secure Web-server And Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes. It also contains fail2ban for intrusion prevention.
|
||||
SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes. It also contains fail2ban for intrusion prevention.
|
||||
|
||||
[](https://linuxserver.io)
|
||||
|
||||
@@ -177,13 +177,16 @@ 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`
|
||||
> * If you don't want to or can't use the option `--remove-orphans`, then you can first do `docker-compose down`, then edit the compose yaml as above, and then issue `docker-compose up -d`
|
||||
|
||||
> 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
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
alpine-baselayout-3.2.0-r7
|
||||
alpine-keys-2.2-r0
|
||||
apache2-utils-2.4.43-r0
|
||||
apache2-utils-2.4.46-r0
|
||||
apk-tools-2.10.5-r1
|
||||
apr-1.7.0-r0
|
||||
apr-util-1.6.1-r6
|
||||
@@ -20,13 +20,13 @@ freetype-2.10.2-r0
|
||||
gdbm-1.13-r1
|
||||
git-2.26.2-r0
|
||||
git-perl-2.26.2-r0
|
||||
glib-2.64.4-r0
|
||||
glib-2.64.5-r0
|
||||
gmp-6.2.0-r0
|
||||
gnupg-2.2.20-r0
|
||||
gnutls-3.6.14-r0
|
||||
icu-libs-67.1-r0
|
||||
ip6tables-1.8.4-r1
|
||||
iptables-1.8.4-r1
|
||||
ip6tables-1.8.4-r2
|
||||
iptables-1.8.4-r2
|
||||
libacl-2.2.53-r0
|
||||
libassuan-2.5.3-r0
|
||||
libattr-2.4.48-r0
|
||||
@@ -74,7 +74,7 @@ libtls-standalone-2.9.1-r1
|
||||
libunistring-0.9.10-r0
|
||||
libuuid-2.35.2-r0
|
||||
libwebp-1.1.0-r0
|
||||
libx11-1.6.11-r0
|
||||
libx11-1.6.12-r0
|
||||
libxau-1.0.9-r0
|
||||
libxcb-1.14-r1
|
||||
libxdmcp-1.1.3-r0
|
||||
@@ -131,8 +131,8 @@ php7-ctype-7.3.21-r0
|
||||
php7-curl-7.3.21-r0
|
||||
php7-dom-7.3.21-r0
|
||||
php7-exif-7.3.21-r0
|
||||
php7-fileinfo-7.3.20-r0
|
||||
php7-fpm-7.3.20-r0
|
||||
php7-fileinfo-7.3.21-r0
|
||||
php7-fpm-7.3.21-r0
|
||||
php7-ftp-7.3.21-r0
|
||||
php7-gd-7.3.21-r0
|
||||
php7-iconv-7.3.21-r0
|
||||
@@ -160,7 +160,7 @@ php7-pgsql-7.3.21-r0
|
||||
php7-phar-7.3.21-r0
|
||||
php7-posix-7.3.21-r0
|
||||
php7-session-7.3.21-r0
|
||||
php7-simplexml-7.3.20-r0
|
||||
php7-simplexml-7.3.21-r0
|
||||
php7-soap-7.3.21-r0
|
||||
php7-sockets-7.3.21-r0
|
||||
php7-sodium-7.3.21-r0
|
||||
@@ -169,7 +169,7 @@ php7-tokenizer-7.3.21-r0
|
||||
php7-xml-7.3.21-r0
|
||||
php7-xmlreader-7.3.21-r0
|
||||
php7-xmlrpc-7.3.21-r0
|
||||
php7-xmlwriter-7.3.20-r0
|
||||
php7-xmlwriter-7.3.21-r0
|
||||
php7-zip-7.3.21-r0
|
||||
pinentry-1.1.0-r2
|
||||
popt-1.16-r7
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
project_name: swag
|
||||
project_url: "https://linuxserver.io"
|
||||
project_logo: "https://github.com/linuxserver/docker-templates/raw/master/linuxserver.io/img/swag.gif"
|
||||
project_blurb: "SWAG - Secure Web-server And Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes. It also contains fail2ban for intrusion prevention."
|
||||
project_blurb: "SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes. It also contains fail2ban for intrusion prevention."
|
||||
project_lsio_github_repo_url: "https://github.com/linuxserver/docker-{{ project_name }}"
|
||||
|
||||
project_blurb_optional_extras_enabled: false
|
||||
@@ -76,13 +76,16 @@ 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`
|
||||
> * If you don't want to or can't use the option `--remove-orphans`, then you can first do `docker-compose down`, then edit the compose yaml as above, and then issue `docker-compose up -d`
|
||||
|
||||
> 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
|
||||
|
||||
Reference in New Issue
Block a user