![Tandoor]()
Tandoor
Stack
The recipe manager that allows you to manage your ever growing collection of digital recipes.
Services
db_recipes
Configuration
ImagepostgresPOSTGRES_DB=postgresPOSTGRES_USER=postgresPOSTGRES_PASSWORD=postgresImage details
recipes
Configuration
Imagevabene1111/recipes82:8080/opt/recipes/staticfiles : /portainer/Files/AppData/Config/tandoor/staticfiles/opt/recipes/mediafiles : /portainer/Files/AppData/Config/tandoor/mediafilesSECRET_KEY=YOUR_SECRET_KEYDB_ENGINE=django.db.backends.postgresqlPOSTGRES_HOST=db_recipesPOSTGRES_PORT=5432POSTGRES_USER=postgresPOSTGRES_PASSWORD=postgresPOSTGRES_DB=postgresunless-stoppedImage details
Standalone Install
Select an install method, to see config/commands for deploying Tandoor
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Tandoor, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
db_recipes:
image: postgres
environment:
- POSTGRES_DB=postgres
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=postgres
recipes:
image: vabene1111/recipes
container_name: tandoor
ports:
- 82:8080
volumes:
- /portainer/Files/AppData/Config/tandoor/staticfiles:/opt/recipes/staticfiles
- /portainer/Files/AppData/Config/tandoor/mediafiles:/opt/recipes/mediafiles
environment:
- SECRET_KEY=YOUR_SECRET_KEY
- DB_ENGINE=django.db.backends.postgresql
- POSTGRES_HOST=db_recipes
- POSTGRES_PORT=5432
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=postgres
- POSTGRES_DB=postgres
restart: unless-stopped
depends_on:
- db_recipes
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/tandoor.yml up -dMore install options in our documentation.
Container Documentation
db_recipes Documentation
The PostgreSQL object-relational database system provides reliability and data integrity.
recipes Documentation
Django application for managing recipes - github.com/vabene1111/recipes
Serve Tandoor on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying tandoor.example.com to http://recipes:8080
Add this to your Caddyfile
tandoor.example.com {
reverse_proxy http://recipes:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:82 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :82 - Stop the other service, or pick a different host port. In
82:8080only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:82. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, tandoor can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 82
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/tandoor/staticfiles(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull postgres
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within tandoor's repo
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Tandoor is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
db_recipesrunspostgresrecipesrunsvabene1111/recipes, starts after db_recipes
Ports
A port is the door the app answers on. A mapping like 82:8080 means it's reachable on port 82 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:82 in a browser. It opens:
82:8080, likely the web interface
Volumes
A volume is where Tandoor keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/opt/recipes/staticfilesfrom/portainer/Files/AppData/Config/tandoor/staticfileson the host/opt/recipes/mediafilesfrom/portainer/Files/AppData/Config/tandoor/mediafileson the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Tandoor takes 7 of them, all with defaults you can leave alone or tweak:
POSTGRES_DB, defaults topostgresPOSTGRES_USER, defaults topostgresPOSTGRES_PASSWORD, defaults topostgresSECRET_KEY, defaults toYOUR_SECRET_KEYDB_ENGINE, defaults todjango.db.backends.postgresqlPOSTGRES_HOST, defaults todb_recipesPOSTGRES_PORT, defaults to5432
Restart policy
The restart policy here is unless-stopped, so Docker restarts Tandoor after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Portainer puts these services on one shared private network, so they can find each other by name (like db_recipes) while only the ports above are open to you.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Tandoor up. Add the template list to Portainer once, then deploying Tandoor is a click rather than a wall of config.