oPodSyncのハードウェア要件：RAM、CPU、ストレージ、SQLite同期データ
PHP、SQLite、ポッドキャスト同期メタデータ、cron更新に対応するoPodSyncハードウェアを計画し、実用的なZimaOSへの導入を推奨する。
oPodSync hardware requirements at a glance
Size oPodSync 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
- Small SQLite/config data plus backups
- Runtime
- PHP 7.4+
- Docker
- No first-party official Docker image
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with upstream facts for oPodSync, 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
- User count
- Subscription count
- Sync action volume
- Feed metadata cron
- SQLite backups
- Web-server choice
- BASE_URL/reverse proxy
- Other containers
Official minimum requirements
Upstream publishes software requirements but no numerical whole-host CPU, RAM, or disk minimum.
Do not turn PHP/SQLite software requirements into invented host minima. oPodSync is a very light metadata service.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Workload is mainly PHP requests and metadata updates. | |
| No numerical official minimum published | Very light metadata workload. | |
| 7.4 or newer | Required upstream. | |
| SQLite3 with JSON1 extension | Required upstream. | |
| No first-party official image | Community images are referenced only. | |
| Optional cron/web-triggered feed metadata refresh | Can run hourly or as needed. | |
| Not required | No GPU workload. |
When to upgrade your hardware
More users
SQLite growth
Host contention
Plan hardware growth with confidence
SSD SQLite storage
Keep the SQLite DB and config on SSD.
SSDMore RAM
Only useful for broader host consolidation.
Higher-RAM hostBackup retention
Store periodic SQLite/config backups on durable storage.
Backup volumeStronger CPU
Rarely needed for oPodSync alone.
Higher-throughput CPU when host-wide load requires itCan it run on ZimaOS?
Install oPodSync from the ZimaOS App Store
A specific public oPodSync App Store page is available.
Open oPodSync in the ZimaOS App Store ↗Preserve the upstream runtime requirements
Use PHP 7.4+ and SQLite3 with JSON1.
Open oPodSync repository ↗Treat Docker as community packaging
Upstream does not maintain an official Docker image, so preserve that distinction.
Review oPodSync Docker note ↗Zima hardware for oPodSync
oPodSync is light enough that ZimaBoard 2 832 is already ample for the service itself.
Choose by workload
Use the smallest reasonable Zima host.
Choose hardware for the rest of the stack rather than oPodSync.
The one-click App Store route does not change the fact that upstream does not maintain a first-party Docker image.
| 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 |
| ZimaBoard 2 1664 | More containers and memory-heavier services | Single-app or small multi-app deployments |
|
CPU throughput is unchanged from the 832 model, so compute-heavy work can still be CPU-limited | 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 oPodSync need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does oPodSync need?
No numerical official CPU minimum is published.
Which PHP version is required?
PHP 7.4 or newer.
Which database does oPodSync use?
SQLite3 with the JSON1 extension.
Does oPodSync have an official Docker image?
No. The upstream project references community images and does not support Docker packaging issues.
Can ZimaBoard 2 832 run oPodSync?
Yes.
Does oPodSync need a GPU?
No.
What data should I back up?
The SQLite database and configuration are the key persistent data.
