Tandoor Recipes is still available in the maintained BigBearCasaOS store, and the current package uses the upstream Tandoor container rather than the old 2024 tutorial state. BigBear currently lists Tandoor 2.6.9 using ghcr.io/tandoorrecipes/recipes.
For a reliable deployment, protect the Postgres database and media/config data, set a real secret key and allowed hosts, and read upstream release notes before upgrading because Tandoor database migrations cannot simply be downgraded.
Use the Current BigBear Package
The maintained BigBearCasaOS app store lists the current Tandoor package and is a better source than the 2024 video alone.
Tandoor Officially Recommends Docker Compose
The current Tandoor Docker guide says Docker/Compose is the officially maintained and regularly tested installation method.
Protect the Database
Production Tandoor uses PostgreSQL in its recommended Compose stack. Keep the database volume on persistent storage and back it up before upgrades.
Protect Recipe Media
Recipe images and uploaded media are part of your data. Verify the CasaOS manifest maps persistent media/static paths rather than keeping them only inside the disposable container filesystem.
Set Strong Secrets
Upstream requires values such as SECRET_KEY, POSTGRES_PASSWORD, and ALLOWED_HOSTS. Do not keep example passwords from a video tutorial.
Tandoor 2 Changed the Container Layout
Tandoor 2 includes nginx inside the web container and exposes port 80 internally. Older tutorials that describe Tandoor 1's gunicorn/media layout can therefore be misleading.
Update with a Backup First
Upstream's current update process is:
docker compose down
docker compose pull
docker compose up -dBut read release notes first. Tandoor warns there is no supported database downgrade path after migrations.
Use HTTPS for Remote Family Access
If recipes need to be reachable outside the LAN, put Tandoor behind authenticated HTTPS or private remote access instead of forwarding the raw application port.
The Docker deployment guide applies to CasaOS custom/community apps too.
Verify the First Start Before Importing Recipes
On the first launch, give the database migrations time to finish and check the web-container and Postgres logs if the UI does not appear. Do not repeatedly recreate the containers while migrations are still running.
Use a Dedicated Host Port
Tandoor 2 serves HTTP through the nginx bundled inside its web container. If CasaOS or another app already uses the selected host port, change only the host-side mapping rather than editing Tandoor's internal port.
Export Recipes as a Second Recovery Path
Database backups are the primary recovery method, but periodic recipe exports give you another way to recover content if the application database is damaged. Keep those exports outside the same container stack.
FAQ
Is Tandoor still in BigBearCasaOS?
Yes. The current repository lists Tandoor 2.6.9.
What database should Tandoor use?
The official Compose setup uses PostgreSQL.
Can I update by pulling a new image?
Yes, but back up first and read release notes because database migrations may not be reversible.
Do I need a reverse proxy?
Not for LAN-only use, but HTTPS/proxying is recommended for remote access.
