You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,16 @@ pnpm install lodash
50
50
51
51
### Production Setup
52
52
53
-
For production or containerized environments, you should deploy NPG with persistent storage and custom configuration:
53
+
For production or containerized environments, you should deploy NPG with persistent storage and custom configuration.
54
+
55
+
**⚠️ Important for Production**: Always deploy NPG behind a reverse proxy (traefik, nginx, Cloudflare, etc.) that handles:
56
+
-**TLS termination** for secure HTTPS connections
57
+
-**Compression** (gzip/brotli) for optimal performance - this is critical for npm metadata. Missing compression can lead to very slow installs.
58
+
-**Custom Domain & Path Setup** - e.g. `https://npg.yourdomain.com/npm` - this is crucial for rewriting URLs correctly for npm clients (esp. pnpm).
59
+
60
+
For now, NPG itself serves uncompressed HTTP traffic and relies on the reverse proxy for these essential production features.
61
+
62
+
> **Coming Soon**: Docker Compose examples for common production scenarios (traefik reverse proxy, Redis caching, multi-instance deployments) will be added to simplify deployment.
0 commit comments