Wealthview Deployment

How Wealthview reaches a server and how it is operated there.

Deploy path

deploy.sh at the repo root deploys over SSH:

DEPLOY_HOST=user@host ./deploy.sh          # DEPLOY_DIR defaults to /opt/wealthview

The production stack is docker-compose.prod.yml with three services — db (PostgreSQL, volume pgdata), app, and backup — plus docker-compose.observability.yml as an optional overlay.

Operating on the server

On a production host, install bin/wv to /usr/local/bin/wv and configure it via /etc/wealthview/wv.conf (template: bin/wv.conf.example) — the source tree is not required on the host. wv then drives the prod compose stack: wv up, wv status, wv logs app, wv psql, backups via the backup service. The full operator handbook is docs/deployment/operations.md in the repo.

Mode detection

The same wv entry point serves dev and prod: prod mode activates when WEALTHVIEW_VERSION is set in .env. When debugging "why is wv using the wrong compose file," check that variable first.

What is deliberately separate

• Wealthview does not share infrastructure with Wikantik — it has its own compose stack, database, and backup service.
• Fleet monitoring: if deployed onto a jakemon-monitored host, it gets host-level metrics for free; app-level scrape targets would be a hosts/<host>/apps.alloy addition in jakemon.

See Also

• Wealthview Development Workflow
• Wealthview Hub
• Home Lab Infrastructure Hub