Skip to main content
store/persistence
<dataDir> is the local path the store resolved (.vendo/data unless you passed a custom one), and <platform> names what doctor detected: Railway, Render, Fly.io, Heroku, or a generic /tmp mount. check: store/persistence · error_code: E-STORE-001 · doctor exits: 0

​
What you’re seeing

This is a warning, not a failure; doctor still exits 0. The app runs fine today. The risk is the next redeploy, which wipes every app your users built and all of their data with it.

​
Why

Without a VENDO_API_KEY, the store defaults to PGlite, which writes to a directory on the local container filesystem. That’s the right default on a laptop or a machine with a real disk. On a platform that recreates its container filesystem on every deploy, it’s a data-loss bug waiting for the next release.

​
The fix

Set VENDO_API_KEY to move onto Vendo Cloud’s hosted store, which survives redeploys by default.
.env.local
Run vendo login if you don’t have a key yet; it mints one and writes it to .env.local for you. This check only runs while no key is set, so once Cloud is wired, it stops firing.
  • E-CFG-002: the gitignore that keeps this same data directory out of git
  • E-CFG-001: a missing .vendo/ config file