Where Does Self-Hosted RecipeSage Store Data?
Self-hosted RecipeSage keeps images and database in compose volumes with config beside them. Exports run JSON-LD, text and PDF.
Last updated
RecipeSage self-hosts through compose with versioned volumes. Postgres plus userdata images carry the instance while search indexes accelerate it. Config beside the stack names every credential.
Exports trade in portable JSON-LD with text and PDF companions. Imports digest rival formats generously. Mobile apps sync the account with offline fallback for kitchens.
Where RecipeSage stores this, by platform
/opt/recipesage/data/userdata
Recipe images on local filesystem per compose mounts with version-varying paths. Postgres carries the database beside it. Confirm pinned compose before archiving.
/opt/recipesage/data/postgres
Database volume with credentials in compose config. Search indexes branch per engine generation. Account sync covers hosted and self-hosted alike.
Frequently asked questions
How do I back up self-hosted RecipeSage?
Archive the Postgres volume with the userdata images tree plus typesearch data per compose version. Config beside the stack names credentials and storage. Mounts vary by selfhost revision, so confirm the pinned file first.
How do I export RecipeSage recipes?
Export JSON-LD for re-importable moves with text and PDF beside it. Imports swallow URLs, images and rival formats including Paprika and Mela. Mobile apps sync the same account with offline fallback.
Which RecipeSage volumes matter?
They split images from search indexes with database beneath. Postgres carries recipes while typesearch powers fuzzy find. Browserless and push services ride alongside without data.
Notice an outdated path? Let us know.