More web workers, PostgreSQL cache, Redis data, plugins and background jobs can turn the 1–2 GB baseline into a bottleneck. Persistent swap activity or OOM events are clear signals for more memory.
Growing communities, plugin-heavy forums and multi-app ZimaOS hosts.Requisiti hardware di Discourse: RAM, CPU, spazio di archiviazione e crescita
Pianifica l’hardware Discourse per RAM, CPU, disco, Docker, PostgreSQL, Redis, caricamenti e crescita della community, con dimensionamenti pratici per un’installazione personalizzata di ZimaOS.
Discourse requirements at a glance
Discourse publishes a clear small-server baseline: a modern single-core CPU, 1 GB RAM with swap and 10 GB disk are the official minimums, while 2+ cores, 2 GB+ RAM and 20 GB+ disk are the current recommended starting points in the cloud install guide. Treat those as the forum stack baseline, not the whole ZimaOS host budget.
- CPU
- Official minimum: modern single-core CPU. Current cloud guide recommends 2+ cores.
- RAM
- Official minimum: 1 GB RAM with swap. Current cloud guide recommends 2 GB+; use more for plugins, traffic, rebuilds and co-hosted ZimaOS apps.
- Storage
- Official minimum: 10 GB. Current cloud guide recommends 20 GB+ before allowing for uploads, backups, logs, Docker layers and host growth.
- Database & cache
- Discourse depends on PostgreSQL and Redis. Their working set, background jobs and forum activity share the same host resources in a standalone deployment.
- GPU
- No GPU is required for the core Discourse forum workload.
- Best Zima starting point
- ZimaBoard 2 832 is a practical small-community starting point; choose 16 GB or a larger storage platform when Discourse shares the host or the community, uploads and backups grow.
From official requirements to the right setup
Start with the official standalone baseline, then add headroom for the database, Redis, Sidekiq background work, uploads, backups, plugins and every other service running on the same ZimaOS system.
-
Official requirements
Use Discourse's official Docker requirements as the floor: 64-bit Linux with Docker, a modern CPU, at least 1 GB RAM with swap and at least 10 GB disk. Prefer the current 2+ core, 2 GB+ RAM and 20 GB+ recommended profile for a new installation.
-
Confirm your needs
Estimate community activity rather than only registered-user count. Concurrent page requests, search, topic creation, email delivery, image processing, plugin behavior and Sidekiq jobs all change CPU and memory pressure.
-
Leave room to grow
Budget storage separately for PostgreSQL data, user uploads, Docker images, logs and backups. A 20 GB starting point is not a long-term capacity plan for an image-heavy or long-running community.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with an adapted Discourse Docker definition. Preserve persistent data, verify hostname, HTTPS/reverse proxy, SMTP or chosen login flow, then monitor RAM, swap, disk latency and backup growth before scaling hardware.
Check every playback client
- Expected active and concurrent forum users
- Plugin count and plugin resource impact
- User-upload and image growth
- PostgreSQL and Redis persistence
- SMTP or alternate login configuration
- HTTPS, domain and reverse-proxy plan
- Backup frequency and retention
- Other ZimaOS apps sharing CPU, RAM and storage
Official minimum requirements
Discourse is unusual among self-hosted web applications because the upstream project publishes a direct hardware floor and a current recommended cloud profile.
The 1 GB/10 GB figures are valid official minimums for the Discourse stack, but they are not a comfortable whole-host target for ZimaOS plus backups and other containers. For a fresh home-server deployment, 8 GB host RAM gives far more practical operating room.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | Modern single-core CPU | Discourse lists dual core as recommended; the current cloud guide expresses this as 1 core minimum and 2+ cores recommended. |
| RAM minimum | 1 GB with swap | This is the official minimum for Discourse itself. The current cloud guide recommends 2 GB+. |
| Disk minimum | 10 GB | The current cloud guide recommends 20 GB+. Uploads, logs, backups and Docker data can require much more over time. |
| Operating system | 64-bit Linux compatible with Docker | Discourse states that the officially supported production installation path is Docker based. |
| Database | PostgreSQL | A standalone deployment includes database workload on the same server unless you intentionally split services. |
| Cache / jobs | Redis 7 plus Rails/Sidekiq services | These services contribute to the real memory and CPU footprint even though they are not separate hardware minimums. |
When to upgrade your hardware
Upgrade when the forum's live workload or data-retention pattern outgrows the host, not simply when the account count reaches an arbitrary number.
RAM pressure and swap become persistent
Uploads, backups and database growth crowd the system disk
Page requests and background jobs compete for CPU
Forum content accumulates continuously. Image-heavy communities and longer backup retention can consume far more storage than the installation baseline and increase restore time.
Long-running communities and sites with frequent media uploads.Higher concurrency, search, email, image processing and Sidekiq queues can keep CPU busy even when storage capacity is still sufficient.
Public communities with sustained activity, imports or heavy automation.Plan hardware growth with confidence
Scale Discourse by removing the actual bottleneck: first protect persistent data and reduce contention, then add CPU or RAM only when monitoring shows the need.
Move persistent data to SSD storage
PostgreSQL, container layers and frequently accessed uploads benefit from predictable low-latency storage, while backups can be retained on larger secondary disks.
Add SATA SSD storage to ZimaBoard 2 or use ZimaCube 2 SSD/HDD tiers; do not keep the only database copy on small onboard eMMC.Add RAM before increasing worker concurrency
More web workers can improve parallel request handling only if PostgreSQL, Redis and the OS still have enough memory. Avoid trading response capacity for constant swapping.
Move from 8 GB to 16 GB when the host runs more apps, plugins or higher concurrency.Separate backups and large uploads from the system volume
Keeping backups and user content away from the small boot volume protects upgrade headroom and simplifies recovery planning.
Use dedicated SATA/NVMe/HDD storage and test restore procedures regularly.Use a larger host when Discourse becomes one service among many
A larger CPU and storage platform makes more sense when the forum shares the server with databases, media, monitoring or other always-on services.
ZimaCube 2 Standard or Pro is justified by consolidation and storage growth, not by Discourse's minimum alone.Can it run on ZimaOS?
Discourse is not currently presented as a one-click ZimaOS App Store app. It can still be self-hosted on ZimaOS through Install Custom App, but the official Discourse deployment uses its own Docker tooling, so an adapted Compose definition should be tested carefully rather than treated as an official one-click package.
Custom install Discourse in ZimaOS
Use Install Custom App from the ZimaOS dashboard with an adapted Docker configuration based on the official Discourse container stack. Persist PostgreSQL, Redis, uploads and application data, and verify the container privileges, hostname, ports and reverse-proxy behavior before production use.
Custom install Discourse in the ZimaOS app ↗Follow the officially supported Docker path
Discourse states that officially supported self-hosting is Docker based on a 64-bit Linux server. Its own installer and launcher automate tuning and container setup, so reproduce those expectations when adapting the deployment to ZimaOS.
Review the official Discourse install path ↗Treat persistence and backups as part of the deployment
A working forum is more than a web container. PostgreSQL, Redis, uploads and backups must survive container recreation and upgrades.
Inspect the official standalone container template ↗Choose Zima hardware for Discourse
Discourse's official baseline is light enough for ZimaBoard 2, but the practical choice depends on active traffic, plugin load, media growth, backups and how many other applications share the host.
Is this a small standalone community or a growing forum on a multi-service host?
Small community or private forum
Start with 8 GB host RAM and SSD-backed persistence; this leaves comfortable headroom over Discourse's official minimum.
- Best starting pointZimaBoard 2 832
- More memory headroomZimaBoard 2 1664
Growing forum, media growth or broader server consolidation
Prioritize storage expansion, backup capacity and stronger multi-service headroom rather than sizing only to the forum container.
- Storage-first platformZimaCube 2 Standard
- Heavier multi-service hostZimaCube 2 Pro
These are workload-based recommendations, not guaranteed concurrent-user or page-view benchmarks. Theme/plugin behavior, web-worker tuning, PostgreSQL cache, Redis, uploads, email jobs, backups and co-hosted services can materially change resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Discourse communities and private forums with SSD-backed persistent data. | Discourse, PostgreSQL, Redis, reverse proxy, backups and a few lightweight ZimaOS services. |
|
Use an added SSD for live forum data and keep independent backups; the 32 GB eMMC should not be the only long-term data location. | Get Now |
| ZimaBoard 2 1664 | A larger Discourse instance or a forum sharing the host with more services. | Higher web/background concurrency, more plugins, larger database cache and additional Docker services. |
|
More memory does not replace fast persistent storage or good backup design, and the N150 remains a compact low-power CPU for very busy public communities. | Get Now |
| ZimaCube 2 Standard | Discourse plus large upload/backup capacity and a broader self-hosted service stack. | Forum data on SSD, longer backup retention, media uploads and multiple always-on ZimaOS applications. |
|
Choose this for storage expansion and platform consolidation; an 8 GB configuration is not automatically better than a 16 GB ZimaBoard 2 for memory-heavy forum workloads. | Get Now |
| ZimaCube 2 Pro | A busier forum combined with databases, monitoring, backups and other server workloads. | Growing Discourse deployment plus multi-service consolidation, faster SSD tiers and high-capacity storage. |
|
This is unnecessary for a small Discourse forum alone; it becomes sensible when CPU, storage and multi-service consolidation all justify the larger system. | 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
These answers cover the main Discourse hardware questions around minimum RAM, CPU, disk, SSD use, Docker, forum growth and ZimaOS deployment.
How much RAM does Discourse need?
Discourse officially lists 1 GB RAM with swap as the minimum. Its current cloud install guide recommends 2 GB+. For a ZimaOS host, 8 GB is a much more practical starting class because the OS, Docker, PostgreSQL, Redis, backups and other apps also consume memory.
Can Discourse run on 1 GB RAM?
Yes, 1 GB with swap is the official minimum, but it is a floor rather than a comfortable modern whole-host target. A low-memory system has little room for plugins, rebuilds, background jobs or other ZimaOS containers and can become swap-bound quickly.
How many CPU cores does Discourse need?
The upstream install guide lists a modern single-core CPU as the minimum and recommends dual core; the current cloud guide expresses this as 1 core minimum and 2+ cores recommended. More concurrency and background work can benefit from additional CPU.
How much storage does Discourse need?
The official minimum is 10 GB and the current cloud guide recommends 20 GB+. Real capacity should include PostgreSQL growth, uploads, Docker data, logs and retained backups, which can exceed the application baseline by a large margin.
Does Discourse need an SSD?
An SSD is not stated as a strict upstream minimum, but it is a strong practical choice for PostgreSQL and container data because forum workloads involve many small database reads and writes. Large backup archives can live on slower secondary storage.
Does Discourse need a GPU?
No. The core Discourse forum stack does not require GPU acceleration. CPU, memory, database I/O, storage capacity and network availability are the relevant hardware dimensions.
Can ZimaBoard 2 run Discourse?
Yes. Both current ZimaBoard 2 configurations exceed Discourse's published CPU and RAM baseline. The 8 GB model is a practical small-community starting point; add SSD storage for persistent data and move to 16 GB when the forum or co-hosted service stack grows.
What makes Discourse hardware needs grow over time?
The biggest drivers are active request concurrency, PostgreSQL working set, Redis and background jobs, plugins, user uploads, image processing, logs and backup retention. Registered-user count alone is a poor sizing metric.
What sources informed this Discourse hardware guide?
The guide uses current Discourse installation documentation for the official minimum and recommended server profile, the official standalone Docker template for service behavior, and current Zima product pages for hardware specifications only.
