4 Commits

Include renames

Author	SHA1	Message	Date
vasyanskandClaude Opus 4.8	74abea5467	fix(deploy): stable container_name for the proxy (avoid pinned-IP collision) ... container_name: spacesh-proxy lets NPM forward by name instead of the fragile pinned 172.18.0.28, which another webproxy container could grab — sending NPM to the wrong target (or itself) and looping. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-15 14:25:31 +07:00
vasyanskandClaude Opus 4.8	4c9eacccb7	fix(deploy): put landing on proxy's network + runtime DNS resolve ... The landing service had no networks: key, so it joined the auto 'default' network while proxy was only on spaceshell-network + webproxy — they shared no network, so proxy_pass to 'landing' couldn't resolve. With a static upstream{ server landing:80 } nginx fails to boot on an unresolvable name and restart-loops, so the proxy flapped (page intermittently up/down). Fixes: - landing now joins spaceshell-network (shared with proxy). - proxy.conf resolves 'landing' at request time via Docker DNS (127.0.0.11) using a variable proxy_pass, so nginx starts even if landing is briefly down. nginx -t passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-15 14:20:33 +07:00
vasyansk	179744d8b3	fixes port	2026-06-15 14:05:18 +07:00
vasyansk	75134b6fac	add deploy	2026-06-15 13:47:50 +07:00