Requisitos de hardware do CraftCMS: RAM, CPU, armazenamento, PHP e base de dados
Planeie o hardware do CraftCMS para memória PHP, MySQL/PostgreSQL, transformações de recursos, filas, armazenamento e recomendações práticas de implementação do ZimaOS.
CraftCMS hardware requirements at a glance
Size CraftCMS from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No whole-host RAM minimum published
- CPU
- No numerical official CPU minimum published
- Storage
- 200 MB free disk minimum
- Database
- MySQL 8.0.17+, MariaDB 10.4.6+, or PostgreSQL 13+
- PHP
- PHP 8.2+; 256 MB PHP memory minimum; 512 MB+ recommended
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with current upstream facts for CraftCMS, then size the real workload instead of generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Users/concurrency
- CPU workload
- RAM headroom
- Database/runtime
- Persistent storage
- Network
- Backups
- Upgrade path
Official minimum requirements
Official upstream requirements for CraftCMS are summarized below.
Keep software/runtime limits separate from whole-host sizing unless upstream explicitly publishes host hardware minimums.
| Requirement | Official minimum | What this supports |
|---|---|---|
| PHP 8.2+ | Craft 5 requirement. | |
| 256 MB allocated to PHP | 512 MB+ recommended; not whole-host RAM. | |
| MySQL 8.0.17+, MariaDB 10.4.6+, or PostgreSQL 13+ | InnoDB for MySQL. | |
| 200 MB free | Assets/backups grow separately. | |
| Composer 2.0+ | Standard project management. | |
| No numerical whole-host minimum published | Workload dependent. | |
| Not required | No GPU baseline. |
When to upgrade your hardware
Higher concurrency
State growth
Host contention
Plan hardware growth with confidence
SSD application state
Keep databases and active app state on SSD.
SSD/NVMeMore RAM
Add memory for database/cache/workers and multi-app hosts.
Higher-memory Zima modelMore capacity
Expand content, attachment, report, or backup storage.
ZimaCube storageStronger CPU
Use higher CPU throughput for heavier dynamic workloads.
ZimaCube 2 ProCan it run on ZimaOS?
Custom install CraftCMS in ZimaOS
No specific public CraftCMS per-app page was verified.
Custom install CraftCMS in the ZimaOS app ↗Meet Craft's PHP/database requirements
Use current supported runtime/database versions.
Open Craft CMS requirements ↗Keep PHP memory distinct from host RAM
Do not report 256 MB as server RAM.
Review Craft hosting guidance ↗Zima hardware for CraftCMS
Choose hardware based on the verified workload, not app-store memory metadata.
Choose by workload
Use the smallest Zima option that clears official/runtime needs.
Scale CPU, RAM, and storage based on the dominant bottleneck.
Recommendations are practical mappings, not upstream hardware certifications unless explicitly stated.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services | Small single-app or multi-app workloads |
|
8 GB RAM can limit heavier Java, search, helpdesk, and AI stacks | Get Now |
| ZimaBoard 2 1664 | Memory-heavier services | Moderate databases and multi-container workloads |
|
CPU remains the 4-core N150 | Get Now |
| ZimaCube 2 Pro | CPU-heavy and database-heavy workloads | Large repositories, helpdesk stacks, reporting, and AI orchestration |
|
16 GB RAM can still be low for large enterprise or 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 CraftCMS need?
No whole-host RAM minimum published.
How much CPU does CraftCMS need?
No numerical official CPU minimum published.
What storage should I plan?
200 MB free disk minimum.
Which database or runtime matters most?
MySQL 8.0.17+, MariaDB 10.4.6+, or PostgreSQL 13+.
Does it need a GPU?
No GPU is required for the base application unless the upstream workload explicitly adds a separate accelerated component.
Can Zima hardware run it?
ZimaBoard 2 832.
What usually triggers an upgrade?
Higher concurrency, database growth, storage growth, or heavier processing.
What should be backed up?
Persistent application data, databases, configuration, and workload-specific content.
