flndrn
запушил(а) main в flndrn/Briven
c1786f7b5e chore(studio): groundwork for studio deploy (dockerignore fix + continuation brief)
Deferred studio deploy to a dedicated session. Banking the groundwork:
- apps/studio/Dockerfile.dockerignore: the root .dockerignore excludes apps/studio/*
(kept out of web/api build contexts). This Dockerfile-specific ignore re-includes
studio source for the studio build only, so `next build` compiles. (Build needs a
6GB heap → build on France, not a 7.7GB local Docker VM.)
- docs/STUDIO-DEPLOY-BRIEF.md: approved phased plan, auth contract (data path uses
requireProjectAuth; login is GoTrue vs Briven-Auth = needs reconciling), known
hurdles (CSS build-order, project-create orgId mismatch), and concrete next steps.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3797e734da fix(doltgres): upgrade 0.56.6→0.57.2 (lock-under-load fix) + rework backups to gentle host job
Root cause of the 2026-08-01 full-platform outage (api.briven.tech 404 for all
tenants): DoltGres 0.56.6 locks its databases under concurrent write load and
serves none, crash-looping the API. Upstream 0.57.1 shipped a lock-subsystem
rewrite + INSERT-panic fix; 0.57.1 also enabled auto-GC by default (GC breaks
all connections).
- compose: pin dolthub/doltgresql:0.57.2 (was @sha256 0.56.6); disable auto-GC
in the volume config (behavior.auto_gc_behavior.enable:false, 0.57.x only).
Validated: 0.57.2 reads 0.56.6 data unchanged; held a full stress test
(373k HTTP req @ 3.1k rps + 10-way write storm, 0 lock/GC errors).
- backups: REMOVE the in-compose dolt-backup sidecar (its un-throttled per-DB
loop helped lock the engine). Rework infra/backups/briven-backup.sh into a
gentle, one-DB-at-a-time, throttled dolt_backup pass on 0.57.2 (primary DR,
restorable via `dolt backup restore`) + pg_dump secondary + off-site mirror.
Runs from the existing systemd timer. Proven safe under monitoring.
- scripts/doltgres-version-check.sh: on-demand pin-vs-latest checker (manual,
infra-compliant — no host-side poller) to keep our version moving with upstream.
- docs/knowledge-base.md: incident write-up, version pinning + tested upgrade
process, emergency-triage recipe, gotchas.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Просмотр сравнение для этих 2 коммитов »
3 недель назад