From 26c26ec805b67689306d6cce7d9298941a4eb3a6 Mon Sep 17 00:00:00 2001 From: baudneo <86508179+baudneo@users.noreply.github.com> Date: Thu, 3 Nov 2022 07:56:35 -0600 Subject: [PATCH 1/2] Update README.md Typos, add info about bullseye image and trivy scans. --- README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2535749c..473ea5e6 100644 --- a/README.md +++ b/README.md @@ -13,10 +13,14 @@

-# Trivy Scan +# Trivy Scan (CVE scanner) - [Buster-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:latest) - [Bullseye-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:bullseye) --- + +# Updated +- Now running Debian Bullseye as base OS. +--- This project comes as a pre-built docker image that enables you to easily forward to your websites running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt. @@ -66,7 +70,7 @@ I won't go in to too much detail here but here are the basics for someone new to version: '3' services: app: - image: 'baudneo/nginx-proxy-manager:latest' + image: 'baudneo/nginx-proxy-manager:bullseye' restart: unless-stopped ports: - '80:80' @@ -140,7 +144,7 @@ Immediately after logging in with this default user you will be asked to modify # ModSecurity _ModSecurity WAF is installed and loaded by default, OWASP-CoreRuleSet is installed and used as the default rule set. The user is responsible for configuring modsecurity via config/CLI._ -__MODSECURITY HAS KNOWN MEMORY LEAKS!__ Whenever `nginx -s reload` is issued expect RAM to increase by 10 to several hundred MB (depending on if you have custom rule files or are double enabling modsec). Nginx is reloaded every time a host is created/modified and when the SSL cert renewal timer resets. The only way to get modsec to release REAM is to restart nginx from inside the running container using `nginx -s stop; nginx -s reload` or by restarting the container using `sudo docker restart [Name of NPM container]` +__MODSECURITY HAS KNOWN MEMORY LEAKS!__ Whenever `nginx -s reload` is issued expect RAM to increase by 10 to several hundred MB (depending on if you have custom rule files or are double enabling modsec). Nginx is reloaded every time a host is created/modified and when the SSL cert renewal timer resets. The only way to get modsec to release RAM is to restart nginx from inside the running container using `nginx -s stop; nginx -s reload` or by restarting the container using `sudo docker restart [Name of NPM container]` ## Environment Variables - `MODSEC_CREATE=1` - Force recreating the default modsecurity config, _This should never be needed_ From 9e2491cb7bfb48b19ccc76f30d1dbfc1d91c106b Mon Sep 17 00:00:00 2001 From: baudneo <86508179+baudneo@users.noreply.github.com> Date: Thu, 3 Nov 2022 07:57:49 -0600 Subject: [PATCH 2/2] Update README.md Wording. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 473ea5e6..b16eae3c 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ --- # Updated -- Now running Debian Bullseye as base OS. +- Now running Debian Bullseye as base OS in the tagged image 'bullseye'. --- This project comes as a pre-built docker image that enables you to easily forward to your websites running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt.