PodFetch-Hardwareanforderungen: RAM, CPU, Speicherplatz und Podcast-Speicher
Planen Sie die PodFetch-Hardware für RAM, CPU, Podcast-Speicher, SQLite oder PostgreSQL sowie Transkripte und erhalten Sie praktische Empfehlungen für die Bereitstellung unter ZimaOS.
PodFetch hardware requirements at a glance
Size PodFetch from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Podcast audio files dominate capacity
- Database
- SQLite by default; PostgreSQL supported
- Docker
- Official image: samuel19982/podfetch:latest
- Best Zima starting point
- ZimaBoard 2 832 for a normal library; ZimaCube for large retained podcast archives
From official requirements to the right setup
Start with upstream facts for PodFetch, then size the workload rather than copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Podcast library size
- Episode retention
- Polling interval
- SQLite vs PostgreSQL
- Full-text transcripts
- Whisper API/local model
- Concurrent listeners
- Backups
Official minimum requirements
Upstream documents Docker, database options, storage paths, and polling but no numerical whole-host CPU, RAM, or disk minimum.
Do not equate optional transcript generation with the base PodFetch requirement. If transcription uses an external OpenAI-compatible Whisper API, the heavy inference is off-host; a local model is a separate AI workload.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Polling and search are light; local AI transcription is separate. | |
| No numerical official minimum published | Depends on library, search, and DB. | |
| samuel19982/podfetch:latest | Current project image. | |
| 8000 | Default application port. | |
| SQLite default; PostgreSQL optional | Configured through DATABASE_URL. | |
| /app/podcasts by default | Can be bind-mounted to another drive. | |
| Not required | Only a separately hosted local transcription model may benefit from GPU. |
When to upgrade your hardware
Podcast archive growth
Database/search growth
Local transcription
Plan hardware growth with confidence
SSD database
Keep SQLite/PostgreSQL data on SSD.
SSDMore RAM
Useful for larger DB/search workloads.
Higher-RAM hostPodcast capacity
Use ZimaCube for large retained audio libraries.
Multi-bay HDD/SSDSeparate AI hardware
Use GPU-capable hardware only if running local transcription models.
Dedicated AI-capable host when requiredCan it run on ZimaOS?
Custom install PodFetch in ZimaOS
No specific public official ZimaOS App Store page was verified for this batch; third-party store availability is not treated as official one-click evidence.
Custom install PodFetch in the ZimaOS app ↗Use the official PodFetch image
The project documents samuel19982/podfetch:latest with podcast and DB volumes.
Open PodFetch installation docs ↗Separate podcasts from database state
Keep the large podcast folder on capacity storage and DB state on SSD.
Review PodFetch storage guidance ↗Zima hardware for PodFetch
PodFetch is generally light; audio retention and optional transcript/search features determine growth.
Choose by workload
Use ZimaBoard with podcast storage on SATA disk.
Storage and optional AI/DB workloads may require larger hardware.
The presence of a third-party ZimaOS/CasaOS app package does not satisfy the SOP requirement for an official public ZimaOS App Store page.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small home-server workloads | Single-app or small multi-app deployments |
|
8 GB RAM and the 4-core N150 can constrain heavier database, extraction, OCR, and multi-service workloads | Get Now |
| ZimaCube 2 Standard | Storage-heavy libraries, downloads, PDFs, podcasts, and retained uploads | Large persistent data sets where drive bays matter most |
|
8 GB RAM can be lower than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavier, database-heavier, and higher-concurrency workloads | Extraction, indexing, many users, or multiple demanding containers |
|
16 GB RAM can still constrain very large databases or local AI workloads | 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
How much RAM does PodFetch need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does PodFetch need?
No numerical official CPU minimum is published.
Which database does PodFetch use?
SQLite by default, with PostgreSQL supported.
Where are podcast files stored?
The default container path is /app/podcasts.
What port does PodFetch use?
8000 by default.
Can ZimaBoard 2 832 run PodFetch?
Yes for a normal personal library.
Does PodFetch need a GPU?
No for the base app; only a separate local transcription model may benefit from GPU.
When should I choose ZimaCube 2?
For large podcast retention, heavier DB/search workloads, or broad consolidation.
