nurdotnet 3b9cf0ee9a docs(stage): how to expose stage externally — DNS + cerbot vs proxmox port ... Stage deploy lands the api+web containers fine (last deploy succeeded), but external 8080/8081 are blocked at the Proxmox/provider firewall (verified: ufw on the VM is inactive, so the block is upstream). Added /etc/nginx/conf.d/food-market-stage.conf on the server: vhost on port 80 (which IS open) for server_name food-market-stage.space-time.kz proxying to 127.0.0.1:8081. Once a DNS A-record is added, certbot can issue Let's Encrypt — same pattern the existing food-market-server uses. docs/stage-access.md — runbook with the three options (DNS subdomain, open Proxmox port, SSH tunnel for quick test). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-22 20:14:00 +05:00
..
24x7.md	ci: move POS (Windows, 2x multiplier) to tag/manual only; document budget	2026-04-22 11:36:29 +05:00
architecture.md	Phase 0: project scaffolding and end-to-end auth	2026-04-21 13:59:13 +05:00
stage-access.md	docs(stage): how to expose stage externally — DNS + cerbot vs proxmox port	2026-04-22 20:14:00 +05:00
stage-setup.md	ci/deploy: stage deploy workflow + notifications + server plan	2026-04-22 13:46:03 +05:00