Thumbnail and image processing create bursty CPU and I/O load.
Large photo migrations.Requisiti hardware di Lychee: RAM, CPU, database e archiviazione delle foto
Pianifica l'hardware Lychee per RAM, CPU, database SQLite o SQL, archiviazione delle foto e Docker, con consigli pratici per un'installazione personalizzata di ZimaOS.
Lychee requirements at a glance
Lychee's app stack is moderate; original photos, thumbnails, database data and import activity are the real capacity drivers.
- RAM
- No numerical official runtime minimum published. The current container keeps the Laravel app in memory through FrankenPHP/Octane.
- CPU
- No numerical official core minimum. Imports, thumbnail generation and image processing create the main CPU bursts.
- Storage
- No universal minimum. Original photos, derived thumbnails, database data and backups determine capacity.
- Database
- SQLite can work without an external database; MySQL, MariaDB and PostgreSQL are supported with an external database service.
- Docker
- Current recommended tags use the new FrankenPHP-based image; legacy nginx/PHP-FPM tags are deprecated.
- Best Zima starting point
- ZimaBoard 2 832 is ample for a modest gallery; ZimaCube 2 Standard/Pro is better for large multi-drive photo libraries.
From official requirements to the right setup
Size Lychee by separating application/database storage from the original photo library.
-
Official requirements
Use the current Lychee Docker image rather than deprecated legacy tags. The new image uses FrankenPHP/Laravel Octane.
-
Confirm your needs
Choose SQLite for a simple deployment or MySQL/MariaDB/PostgreSQL when you want a separate database service.
-
Leave room to grow
Estimate original photo size plus thumbnails and imports. Image processing creates CPU bursts even when gallery browsing is light.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with lycheeorg/lychee, persist its data paths, and place the photo library on durable storage.
Check every playback client
- Photo library size
- Import frequency
- SQLite or external DB
- Thumbnail growth
- Persistent uploads
- Backup retention
- HTTPS/domain
- Other ZimaOS media apps
Official minimum requirements
Lychee's current official container documentation defines image architecture and database options but does not publish numerical host CPU/RAM/disk minimums.
Do not invent a fixed RAM/core requirement. The current deployment should be sized from photo volume, image-processing bursts, database choice and other services on the host.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Current container architecture changes runtime behavior but does not define a fixed RAM floor. |
| CPU minimum | No numerical official minimum published | Photo imports and thumbnails are CPU-sensitive. |
| Storage minimum | No numerical official minimum published | Originals, thumbnails and backups dominate capacity. |
| SQLite | Supported | No external database needed for the simple path. |
| External databases | MySQL, MariaDB or PostgreSQL | Supported when configured externally. |
| Current Docker runtime | FrankenPHP + Laravel Octane | Recommended current image; legacy nginx/PHP-FPM tags are deprecated. |
When to upgrade your hardware
Lychee should scale when image processing or photo-library capacity outgrows the current host.
Large imports make processing slow
Originals and thumbnails outgrow storage
Database and other media apps compete for resources
Media capacity usually becomes the first long-term constraint.
High-resolution and RAW-heavy libraries.A broader NAS/photo stack can create whole-host contention.
All-in-one media servers.Plan hardware growth with confidence
Scale Lychee around durable photo storage and import-processing performance.
Keep database/app data on SSD
Fast storage helps metadata, database and thumbnail operations.
Use SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 8–16 GB for gallery/app headroom
Provides room for the current runtime, database and other home-server services.
ZimaBoard 2 832 or 1664.Use multi-drive storage for large libraries
Original photos and backups dominate long-term capacity.
ZimaCube 2 Standard.Use stronger CPU for heavy import bursts
More general-purpose CPU helps large image-processing/import jobs.
ZimaCube 2 Pro.Can it run on ZimaOS?
Lychee is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App using Lychee's current official container.
Custom install Lychee in ZimaOS
Use Install Custom App with lycheeorg/lychee, persist its required data paths, and attach durable photo storage plus an external database if desired.
Custom install Lychee in the ZimaOS app ↗Use the current FrankenPHP image
Lychee's current Docker release moved to FrankenPHP/Laravel Octane; legacy nginx/PHP-FPM tags are deprecated.
Review Lychee Docker image ↗Choose database layout deliberately
SQLite is available for a simple deployment; MySQL/MariaDB/PostgreSQL require an external database service.
Review Lychee Docker prerequisites ↗Choose Zima hardware for Lychee
Lychee is light enough for ZimaBoard 2, while large photo libraries benefit from ZimaCube's multi-drive storage.
Is this a modest personal gallery or a large photo archive?
Modest personal gallery
Use ZimaBoard 2 with SSD-backed app/database data and attached photo storage.
- Best starting pointZimaBoard 2 832
- More app headroomZimaBoard 2 1664
Large photo archive / frequent imports
Use ZimaCube for multi-drive capacity and stronger import-processing CPU.
- Storage-first platformZimaCube 2 Standard
- Higher-processing headroomZimaCube 2 Pro
These are practical workload recommendations, not official photo-count or thumbnail-throughput guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small and medium Lychee galleries. | Lychee, SQLite/small SQL database, normal browsing and imports. |
|
Add sufficient external photo storage; media capacity is more important than app compute. | Get Now |
| ZimaBoard 2 1664 | Larger galleries and broader media stacks. | More database/runtime headroom plus other photo/media apps. |
|
16 GB is practical headroom, not an official Lychee minimum. | Get Now |
| ZimaCube 2 Standard | Large photo libraries. | Lychee plus six-bay original-photo storage and backups. |
|
Choose it primarily for storage topology. | Get Now |
| ZimaCube 2 Pro | Large libraries with heavier import/index work. | Stronger CPU, 16 GB RAM and expandable photo storage. |
|
Actual import speed depends on image formats and storage performance. | 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 Lychee RAM, CPU, databases, photo storage, Docker and ZimaOS deployment.
How much RAM does Lychee need?
Lychee does not publish a numerical official server RAM minimum.
How many CPU cores does Lychee need?
No numerical official core minimum is published; imports and thumbnail generation create the main CPU load.
Which database can Lychee use?
SQLite is supported for a simple deployment; MySQL, MariaDB and PostgreSQL can be used as external databases.
What changed in Lychee Docker?
The current recommended image uses FrankenPHP with Laravel Octane, while legacy nginx/PHP-FPM tags are deprecated.
How much storage does Lychee need?
No universal minimum is published; original photos, thumbnails and backups determine capacity.
Does Lychee need a GPU?
No dedicated GPU is required for normal gallery and image-processing use.
Can ZimaBoard 2 run Lychee?
Yes. The 8 GB model is ample for a modest personal gallery with suitable attached photo storage.
When should I choose ZimaCube 2?
When photo-library capacity, backups or frequent large imports justify multi-drive storage and stronger CPU.
What sources informed this Lychee hardware guide?
The guide uses the current Lychee Docker and project documentation plus current Zima product pages.
