Skip to content

Commit 26c26ec

Browse files
authored
Update README.md
Typos, add info about bullseye image and trivy scans.
1 parent 112185c commit 26c26ec

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,14 @@
1313
</a>
1414
</p>
1515

16-
# Trivy Scan
16+
# Trivy Scan (CVE scanner)
1717
- [Buster-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:latest)
1818
- [Bullseye-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:bullseye)
1919
---
20+
21+
# Updated
22+
- Now running Debian Bullseye as base OS.
23+
---
2024
This project comes as a pre-built docker image that enables you to easily forward to your websites
2125
running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt.
2226

@@ -66,7 +70,7 @@ I won't go in to too much detail here but here are the basics for someone new to
6670
version: '3'
6771
services:
6872
app:
69-
image: 'baudneo/nginx-proxy-manager:latest'
73+
image: 'baudneo/nginx-proxy-manager:bullseye'
7074
restart: unless-stopped
7175
ports:
7276
- '80:80'
@@ -140,7 +144,7 @@ Immediately after logging in with this default user you will be asked to modify
140144
# ModSecurity
141145
_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._
142146

143-
__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]`
147+
__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]`
144148

145149
## Environment Variables
146150
- `MODSEC_CREATE=1` - Force recreating the default modsecurity config, _This should never be needed_

0 commit comments

Comments
 (0)