You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Shared Alchemy state: postgresState on Neon instead of the git-dir symlink #2237
Today Alchemy.localState() sits under a symlink into the git common dir, with our own lock (packages/cli/src/state.ts). That works on one machine only, so a deploy from CI or the cloud office starts from empty state.
Alchemy's postgresState() (docs) keeps state in Postgres and takes a per-(stack, stage) advisory lock, and we already create Neon. Pick that over Cloudflare.state(): that store's locking isn't documented, and its Worker sends telemetry even with DO_NOT_TRACK set. Move existing state across with State.Sync/Export. Needs the owner's database URL secret (varlock), so the cutover is an owner step.
Activity
Plan: Worker Previews on demand and postgresState on Neon (Part of #2238