OutlineWiki Docker Compose & Nginx WebSocket Proxy Runbook
Hostinger KVM NVMe
OutlineWiki 8GB pick (90,000 IOPS) — KVM 4 (4 vCPU / 16GB DDR5 / 200GB NVMe)
InterServer Price-Lock KVM & ZFS
Low-RTT node for outline Node.js + Hocu (19 ms CRDT sync)
UltaHost Dedicated EPYC VDS
Steady OutlineWiki secondary tier (25–100 collaborative editors)
Nginx drops real-time Outline cursors unless WebSocket upgrade headers stay explicit.
In our audit of self-hosted Outline Wiki deployments on OutlineWiki, most 502 Bad Gateway incidents trace back to missing Upgrade and Connection headers or undersized proxy_read_timeout values on /realtime endpoints.
We recommend pinning Outline Node.js at 950 MB base memory plus 12 MB per active editor socket behind HTTP/2 and TLS 1.3.
OutlineWiki Reference Configuration for Outline Docker Compose & Nginx WebSocket
server {
listen 443 ssl http2;
server_name wiki.example.internal;
client_max_body_size 100m;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto https;
proxy_read_timeout 300s;
}
}OutlineWiki Implementation Checklist: Outline Docker Compose & Nginx WebSocket
Phase 1: Outline Docker Compose & Nginx WebSocket
Pin OutlineWiki container memory to 950 MB + (editors * 12 MB) and enable Redis 7 (256 MB) + PostgreSQL 16 (768 MB).
Phase 2: Outline Docker Compose & Nginx WebSocket
Set client_max_body_size to 100m only for API metadata; route binary uploads directly to MinIO presigned URLs.
Phase 3: Outline Docker Compose & Nginx WebSocket
Configure proxy_read_timeout 300s so Yjs collaborative WebSocket sessions survive idle reading intervals.
Phase 4: Outline Docker Compose & Nginx WebSocket
Verify TLS certificate SAN covers both wiki.domain and s3.domain before activating OIDC callbacks.
OutlineWiki Infrastructure Recommendation for Outline Docker Compose & Nginx WebSocket
Verify WebSocket 101 Switching Protocols in browser DevTools before inviting editors.
Our sizing formula on OutlineWiki pairs this Nginx WebSocket configuration with a Hostinger KVM 2 (2 vCPU, 8 GB RAM, 100 GB NVMe at $11.99/mo promo) so TLS termination and Node.js event loops never contend for swap.
OutlineWiki Hardware Ledger: NVMe Throughput vs Base Price
Packet-to-Disk Path for outline Node.js + Hocuspocus Yjs CRDT + OIDC on OutlineWiki
[+] Key Infrastructure Pros
- Keeps outline.env buffers stable at 100 collaborative editors via 8GB compute.
- Protects 19 ms CRDT sync objectives under heavy Postgres tsvector document graph + MinIO assets writes (90,000 IOPS).
- Trims OutlineWiki 3-year infrastructure bills 70%–85% versus metered SaaS seats.
[-] Operational Constraints
- Unlocking $10.49/mo on Hostinger KVM NVMe depends on annual commitment rather than 1m billing.
- Base OS templates need outline.env tuning (WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150) before peak load.
Deploy This OutlineWiki Stack If
- DevOps squads standardizing outline Node.js + Hocuspocus Yjs CRDT + OIDC (100 collaborative editors) on KVM nodes.
- Builders needing root access to set WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150 in outline.env.
When To Choose Alternatives
- Two-day load tests where InterServer Price-Lock KVM & ZFS pay-per-hour beats annual commitments.
- Mandates requiring vendor-staffed 24/7 NOC contracts with zero SSH access.
$10.49/mo