Measure CPU, database queries and media writes during a realistic import batch. Reduce overlapping imports before upgrading.
Bulk cookbook migrations.Hårdvarukrav för Tandoor Recipes: RAM, CPU, lagring, PostgreSQL och receptmedia
Planera RAM, CPU, PostgreSQL och lagring för receptbilder i Tandoor Recipes, med Docker-driftsättning, importarbetsbelastningar och praktiska hårdvarurekommendationer för ZimaOS.
Tandoor Recipes hardware requirements at a glance
The reviewed Tandoor Docker documentation publishes no numerical host minimum. PostgreSQL, recipe imports, uploaded images and database/media backups determine the practical workload. Tandoor 2 uses an integrated web server and no longer builds arm/v7 images.
- RAM
- No numerical official minimum published. Include the application and PostgreSQL, plus import activity and other host services.
- CPU
- No numerical official minimum published. Concurrent use, recipe parsing/imports and image handling create the relevant activity.
- Storage
- Budget PostgreSQL data, recipe media, static files, exports and independent backups. Uploaded images can outweigh recipe text.
- Database
- The maintained Docker Compose examples use PostgreSQL; the reviewed example pins postgres:16-alpine. Do not promote a development SQLite setup as equivalent production guidance.
- Docker / architecture
- The official image is vabene1111/recipes. Tandoor 2 integrates nginx, exposes container port 80 and no longer builds arm/v7 images; use the matching amd64 release on Zima.
- Best Zima starting point
- ZimaBoard 2 832 with durable database/media storage is a practical household recipe server. Select 1664 for additional services rather than a fabricated app minimum.
From official requirements to the right setup
Plan the complete Tandoor Recipes workload before selecting a server.
-
Official requirements
Use the maintained Tandoor 2 Docker Compose example and a stable image. Confirm the database service, secrets and allowed-host settings instead of copying an old multi-container web-server layout.
-
Confirm your needs
Estimate household users, bulk recipe imports, image sizes and optional connector activity. A static recipe collection is different from repeated large imports or a busy shared cookbook.
-
Leave room to grow
Persist PostgreSQL, mediafiles and required static data. Back up the database and uploaded media together, including secrets needed for recovery; an image replacement is not a data backup.
-
Run it on ZimaOS
Use ZimaOS Custom Install with the official app/database services and remap container port 80 to a free host port. Set SECRET_KEY, ALLOWED_HOSTS, database credentials and reverse-proxy headers for the actual hostname.
Check every playback client
- Current Tandoor 2 image/tag
- Concurrent users
- Bulk recipe import size
- Recipe image count and size
- PostgreSQL data volume
- Media/static persistent paths
- SECRET_KEY and ALLOWED_HOSTS
- Free host port / proxy headers
Official minimum requirements
Reviewed October 30, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.
There is no numerical official host minimum in the reviewed Docker guide. PostgreSQL plus uploaded media must fit the host. Do not reuse a source-build requirement, historical SQLite example or unsupported ARM image as production hardware guidance.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Host RAM | No numerical official minimum published. | Database, request concurrency and imports determine whole-host memory. |
| CPU cores | No numerical official minimum published. | Do not infer a CPU minimum from a small single-user demo. |
| Disk capacity | No numerical official minimum published. | Recipe media, PostgreSQL, exports and backups set the capacity budget. |
| Database deployment | PostgreSQL in maintained Compose examples | The reviewed example uses postgres:16-alpine; preserve release-compatible database configuration. |
| Official image | vabene1111/recipes | Use a stable release image instead of beta/develop for routine deployment. |
| Runtime / architecture | Tandoor 2 includes nginx; arm/v7 images no longer built | Prebuilt amd64 container on Zima avoids source-build dependencies. |
| Persistent paths / port | Database, mediafiles and staticfiles; app port 80 | Choose a free host mapping; the ZimaOS UI or another proxy may already own 80. |
When to upgrade your hardware
Use observed Tandoor Recipes workload pressure to decide when an upgrade is warranted.
Imports slow normal use
Database and other apps create memory pressure
Images and retained backups fill storage
Inspect application processes and PostgreSQL together, then size the shared host from observed peaks.
Recipe server on a consolidated host.Track uploaded media separately from text records and reserve working space for exports and restores.
Long-lived image-rich collections.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use reliable active storage
Place PostgreSQL and recipe media on durable storage with recoverable backups.
ZimaBoard 2 with SATA/PCIe SSD.Add RAM for shared applications
Choose more memory when the complete container stack needs it; CPU remains unchanged.
ZimaBoard 2 1664.Size media and backup retention
Add capacity based on actual image growth and retained database/media copies.
Additional SSD storage; multi-drive NAS only if broader archives justify it.Resolve the actual import bottleneck
Check database I/O, CPU and upstream recipe-source delays separately.
Keep a modest host for ordinary household use.Can it run on ZimaOS?
No specific public official one-click Tandoor Recipes ZimaOS page was verified. Use the maintained upstream Compose topology through Custom Install.
Custom install Tandoor Recipes in ZimaOS
Deploy vabene1111/recipes with the documented PostgreSQL service, persistent database/media/static paths and actual hostname/secrets. Map container port 80 to an unused host port.
Custom install Tandoor Recipes in the ZimaOS app ↗Use the official Tandoor Recipes deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Tandoor Recipes official installation ↗Review database and application configuration
Keep allowed hosts, secret key, database connectivity and reverse-proxy headers aligned with current Tandoor 2 guidance.
Review Tandoor Recipes deployment details ↗Which Zima hardware fits Tandoor Recipes?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Tandoor Recipes deployment?
Household recipe collection
Start with reliable database and image storage.
- Workload optionZimaBoard 2 832
Recipes plus a wider home-server stack
Select RAM for the combined applications.
- Workload optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Household cookbook | Tandoor, PostgreSQL and modest import/media activity. |
|
8 GB is a practical shared-host choice, not an official Tandoor requirement. | Get Now |
| ZimaBoard 2 1664 | Cookbook with other services | More memory headroom for PostgreSQL and companion apps. |
|
The same N150 CPU remains; additional RAM does not fix slow external recipe sources. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
Answers to Tandoor Recipes RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM does Tandoor Recipes require?
No numerical official minimum is published in the reviewed Docker guide. Budget the application, PostgreSQL and host OS together, and measure an import rather than only idle usage.
Does Tandoor need a powerful CPU?
No numerical core minimum is published in the reviewed deployment guide. Concurrent imports, parsing and image handling determine practical compute; ordinary household browsing is a different workload.
Which database should I deploy?
Follow the maintained PostgreSQL Compose example. The reviewed example uses PostgreSQL 16. Do not confuse a development SQLite setup or an older add-on recipe with current maintained Docker guidance.
How much storage does a recipe server need?
Count uploaded recipe images, PostgreSQL data, exports and backups separately. Recipe text alone often understates the actual archive.
Does Tandoor need a GPU or ARM-specific hardware?
No GPU is required for the normal recipe workflow. Tandoor 2 no longer builds arm/v7 images; select the amd64 container on Zima hardware and confirm any optional external AI backend independently.
Can ZimaBoard 2 run Tandoor?
It is a practical household recipe host with durable database/media volumes. Choose 16 GB when other co-hosted services need it, not because Tandoor has a published 16 GB minimum.
Why do old Docker examples fail on Tandoor 2?
Tandoor 2 includes nginx and changed deployment details. Use the current Compose guide, retain valid secrets/allowed hosts and avoid conflicting host port 80 ownership.
When should I choose ZimaCube 2?
Choose it for broader multi-drive archives or measured combined-server demand. A normal recipe collection alone does not justify a higher storage or GPU tier.
What sources informed this Tandoor Recipes hardware guide?
This guide was reviewed against the linked project deployment documentation on October 30, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.
