Bot Updating Package Versions

2026-03-10 04:05:16 +09:00 · 2022-07-21 07:32:51 +02:00 · 2022-07-14 07:34:38 +02:00 · 2022-07-08 12:46:30 +02:00 · 2022-07-08 05:37:38 -05:00 · 2022-07-07 21:01:12 -05:00
3 changed files with 12 additions and 12 deletions
--- a/README.md
+++ b/README.md
@@ -94,8 +94,8 @@ This will *ask* Google et al not to index and list your site. Be careful with th

 * This container includes auto-generated pfx and private-fullchain-bundle pem certs that are needed by other apps like Emby and Znc.
  * To use these certs in other containers, do either of the following:
-  1. *(Easier)* Mount the container's config folder in other containers (ie. `-v /path-to-le-config:/le-ssl`) and in the other containers, use the cert location `/le-ssl/keys/letsencrypt/`
-  2. *(More secure)* Mount the SWAG folder `etc` that resides under `/config` in other containers (ie. `-v /path-to-le-config/etc:/le-ssl`) and in the other containers, use the cert location `/le-ssl/letsencrypt/live/<your.domain.url>/` (This is more secure because the first method shares the entire SWAG config folder with other containers, including the www files, whereas the second method only shares the ssl certs)
+  1. *(Easier)* Mount the container's config folder in other containers (ie. `-v /path-to-swag-config:/swag-ssl`) and in the other containers, use the cert location `/swag-ssl/keys/letsencrypt/`
+  2. *(More secure)* Mount the SWAG folder `etc` that resides under `/config` in other containers (ie. `-v /path-to-swag-config/etc:/swag-ssl`) and in the other containers, use the cert location `/swag-ssl/letsencrypt/live/<your.domain.url>/` (This is more secure because the first method shares the entire SWAG config folder with other containers, including the www files, whereas the second method only shares the ssl certs)
  * These certs include:
  1. `cert.pem`, `chain.pem`, `fullchain.pem` and `privkey.pem`, which are generated by Certbot and used by nginx and various other apps
  2. `privkey.pfx`, a format supported by Microsoft and commonly used by dotnet apps such as Emby Server (no password)
--- a/package_versions.txt
+++ b/package_versions.txt
@@ -7,7 +7,7 @@ apr-util-1.6.1-r7
 argon2-libs-20190702-r1
 bash-5.1.16-r0
 brotli-libs-1.0.9-r5
-busybox-1.33.1-r7
+busybox-1.33.1-r8
 c-client-2007f-r11
 ca-certificates-20211220-r0
 ca-certificates-bundle-20211220-r0
@@ -17,8 +17,8 @@ expat-2.4.7-r0
 fail2ban-0.11.2-r0
 freetype-2.10.4-r3
 gdbm-1.19-r0
-git-2.32.2-r0
-git-perl-2.32.2-r0
+git-2.32.3-r0
+git-perl-2.32.3-r0
 glib-2.68.3-r0
 gmp-6.2.1-r1
 gnupg-2.2.31-r1
@@ -92,8 +92,8 @@ mpdecimal-2.5.1-r1
 musl-1.2.2-r3
 musl-utils-1.2.2-r3
 nano-5.7-r2
-ncurses-libs-6.2_p20210612-r0
-ncurses-terminfo-base-6.2_p20210612-r0
+ncurses-libs-6.2_p20210612-r1
+ncurses-terminfo-base-6.2_p20210612-r1
 nettle-3.7.3-r0
 nghttp2-libs-1.43.0-r0
 nginx-1.20.2-r1
@@ -118,13 +118,13 @@ nginx-mod-stream-geoip2-1.20.2-r1
 nginx-vim-1.20.2-r1
 npth-1.6-r0
 oniguruma-6.9.7.1-r0
-openssl-1.1.1o-r0
+openssl-1.1.1q-r0
 p11-kit-0.23.22-r0
 pcre-8.44-r0
 pcre2-10.36-r1
 perl-5.32.1-r0
 perl-error-0.17029-r1
-perl-git-2.32.2-r0
+perl-git-2.32.3-r0
 php7-7.4.26-r0
 php7-bcmath-7.4.26-r0
 php7-bz2-7.4.26-r0
@@ -216,7 +216,7 @@ scanelf-1.3.2-r0
 shadow-4.8.1-r0
 skalibs-2.10.0.3-r0
 sqlite-libs-3.35.5-r0
-ssl_client-1.33.1-r7
+ssl_client-1.33.1-r8
 tzdata-2022a-r0
 unixodbc-2.3.9-r1
 utmps-0.1.0.2-r0
--- a/readme-vars.yml
+++ b/readme-vars.yml
@@ -111,8 +111,8 @@ app_setup_block: |

  * This container includes auto-generated pfx and private-fullchain-bundle pem certs that are needed by other apps like Emby and Znc.
    * To use these certs in other containers, do either of the following:
-    1. *(Easier)* Mount the container's config folder in other containers (ie. `-v /path-to-le-config:/le-ssl`) and in the other containers, use the cert location `/le-ssl/keys/letsencrypt/`
-    2. *(More secure)* Mount the SWAG folder `etc` that resides under `/config` in other containers (ie. `-v /path-to-le-config/etc:/le-ssl`) and in the other containers, use the cert location `/le-ssl/letsencrypt/live/<your.domain.url>/` (This is more secure because the first method shares the entire SWAG config folder with other containers, including the www files, whereas the second method only shares the ssl certs)
+    1. *(Easier)* Mount the container's config folder in other containers (ie. `-v /path-to-swag-config:/swag-ssl`) and in the other containers, use the cert location `/swag-ssl/keys/letsencrypt/`
+    2. *(More secure)* Mount the SWAG folder `etc` that resides under `/config` in other containers (ie. `-v /path-to-swag-config/etc:/swag-ssl`) and in the other containers, use the cert location `/swag-ssl/letsencrypt/live/<your.domain.url>/` (This is more secure because the first method shares the entire SWAG config folder with other containers, including the www files, whereas the second method only shares the ssl certs)
    * These certs include:
    1. `cert.pem`, `chain.pem`, `fullchain.pem` and `privkey.pem`, which are generated by Certbot and used by nginx and various other apps
    2. `privkey.pfx`, a format supported by Microsoft and commonly used by dotnet apps such as Emby Server (no password)
Author	SHA1	Message	Date
LinuxServer-CI	4864761b54	Bot Updating Package Versions	2022-07-21 07:32:51 +02:00
LinuxServer-CI	3d70935ecf	Bot Updating Package Versions	2022-07-14 07:34:38 +02:00
LinuxServer-CI	e5b672e52b	Bot Updating Package Versions	2022-07-08 12:46:30 +02:00
Eric Nemchik	1adf35b5df	Merge pull request #246 from linuxserver/minor-readme-update Minor readme update	2022-07-08 05:37:38 -05:00
Eric Nemchik	c279c173b3	Minor readme update	2022-07-07 21:01:12 -05:00