Installation

QuoteNode runs as Docker containers. You do not need to install Java, Node.js, PostgreSQL, or Gotenberg on the host for normal deployments. The main decision is where the application will be reachable from: only your laptop, an office LAN, or the public internet.

Choose your deployment path

Topology	URL model	Public offer links	Email links	HTTPS	Intended use
Laptop/local	http://localhost	only same machine	not useful for external clients	no	trial/demo
LAN Windows	http://<pc-ip> or local DNS	only LAN clients	only internal recipients	optional/internal	office-only trial
LAN Linux server	http://<server-ip> or local DNS	only LAN/VPN clients	internal unless reachable	optional/internal	internal sales team
WAN Ubuntu VPS	public domain + HTTPS	works for customers	works if SMTP/domain configured	required	beta production
Portainer/QNAP/NAS	host-specific Docker UI	depends on routing/NAT/domain	depends on routing/SMTP	required for customer links	advanced home/SMB ops
Coolify	public domain + managed proxy	works for customers	works if SMTP/domain configured	managed by Coolify	easiest public deployment

Installation guides

• Local laptop — quick evaluation on one machine.
• Windows LAN server — Docker Desktop on a PC reachable inside an office network.
• Linux LAN server — Docker Engine on an internal server or VM.
• Ubuntu public server — public domain, HTTPS, SMTP, backups, and firewall basics.
• Coolify — Docker Compose deployment behind Coolify’s proxy.
• Portainer, QNAP, or NAS — advanced self-hosting notes for Docker UI platforms.

Shared references

• Deployment environment variables — minimal operator-oriented variables for installation guides.
• Installation troubleshooting — common link, CORS, SMTP, DNS, and secret-loss problems.
• Environment Variables Reference — full variable catalog.
• Backup & Recovery — backup strategy and restore notes.
• Deployment Options — architecture-level deployment overview.

Before you publish links

QuoteNode can generate public offer links, notification preference links, and email messages. Those links only work for recipients who can reach the same URL that the browser uses.

• A link generated on http://localhost works only on that same machine.
• A link generated on http://192.168.x.x works only for people on that LAN or VPN.
• A link generated on https://crm.example.com works publicly only when DNS, HTTPS, proxy routing, and firewalls are configured correctly.
• Email delivery requires SMTP. Manual PDF download and manual public-link sharing do not.

Minimum resources

Deployment	RAM	CPU	Disk
Evaluation / solo use	2 GB	1 core	10 GB SSD
Small team	4 GB	2 cores	20 GB SSD
Larger beta workspace	8 GB	4 cores	50 GB SSD

These are conservative starting points. Large catalogs, frequent PDF generation, many backups, and product images increase storage and memory needs.

For per-service container limits, RAM/CPU tuning, and how to avoid out-of-memory issues, see System Resources & Tuning.