chore(prod): move prod redis to Hyper-V HA cluster (drop sidecar)#74
Merged
Conversation
Production (bidwright.rassaun.com) no longer runs a bundled redis. It now uses the shared Hyper-V HA redis — REDIS_URL in the Dokploy env points at the floating master VIP 10.0.0.90:6379 on db 4 (isolated keyspace; the instance is maxmemory-policy=noeviction, which BullMQ requires). The VIP follows the current master on failover, same model as the pg .85 VIP, so the worker's URL-only IORedis client needs no Sentinel code. - remove the `redis` service + its depends_on in api/worker - remove the `bidwright-redisdata` volume - point the REDIS_URL default at the Hyper-V VIP (real creds in Dokploy env) Postgres and redis remain BUNDLED in the self-host/server compose files (docker-compose.prod.yml, docker-compose.hosted.yml, scripts/launcher, base docker-compose.yml), and desktop keeps embedded-postgres — only the Rassaun prod Dokploy stack externalizes these stateful services. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Externalizes redis for the production Dokploy stack (
bidwright.rassaun.com), mirroring the earlier DB→cluster and files→NAS moves (#73). Applied live to the Dokploy raw compose + env and redeployed; this updates the repo mirror.Changes (
docker-compose.prod-registry.yml)redisservice, itsdepends_onin api/worker, and thebidwright-redisdatavolume.REDIS_URL(in the Dokploy env) now points at the shared Hyper-V HA redis — floating master VIP10.0.0.90:6379on db 4 (isolated keyspace; instance ismaxmemory-policy noeviction, required by BullMQ). The VIP follows the current master on failover, same model as the pg.85VIP, so the worker's URL-only IORedis client needs no Sentinel code.Bundling preserved (per request)
Postgres + redis stay bundled in the self-host/server shapes —
docker-compose.prod.yml,docker-compose.hosted.yml,scripts/launcher/docker-compose.yml, basedocker-compose.yml— and desktop keeps embedded-postgres (it has never bundled redis; it runs api+web in-process). Only the Rassaun prod stack externalizes these.Verification (prod, post-cutover)
done; api/worker/web healthy;bidwright-redis-1sidecar removed.db4on10.0.0.90now holdsbull:bidwright-*keys; apiREDIS_URL=redis://:***@10.0.0.90:6379/4./→ 200.Also cleaned up the defunct
redis-ha-comotoDokploy remnant (orphaned config dir; no services/volumes remained). The sharedinfra-netoverlay was left intact (used by adminapp2/beacon/minio/etc.).🤖 Generated with Claude Code