Configuration matérielle requise pour LazyLibrarian : RAM, processeur, stockage et stockage de bibliothèque
Planifier le matériel pour LazyLibrarian : RAM, CPU, stockage d’ebooks et de livres audio, Python, Docker et recommandations pratiques de déploiement sur ZimaOS.
LazyLibrarian hardware requirements at a glance
Size LazyLibrarian from verified upstream requirements first, then add headroom for the real workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Size for ebooks, audiobooks, magazines, covers, metadata, downloads, and backups
- Runtime
- Python 3.7+ for source install
- Port
- Default web UI port 5299
- Best Zima starting point
- ZimaBoard 2 832 for a small library
From official requirements to the right setup
Treat LazyLibrarian as a media-library automation workload: metadata scans, import/conversion tools, download clients, and retained ebooks or audiobooks all affect sizing.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Library size
- Audiobook size
- Download staging
- Calibre conversion
- FFmpeg use
- Metadata scans
- Downloader integration
- Backup retention
Official minimum requirements
Upstream documents Python, port, and installation paths but no numerical whole-host CPU, RAM, or disk minimum.
Do not use the ZimaOS store memory field as an upstream official minimum. Storage capacity and optional processing tools drive growth.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Processing tools drive compute use. | |
| No numerical official minimum published | Depends on library scale and tools. | |
| Python 3.7 or higher | Later is recommended. | |
| 5299 | Web UI port. | |
| Third-party Docker packages documented | Project links LinuxServer and others. | |
| ebooks, audiobooks, covers, metadata, magazines | Retained media dominates capacity. | |
| Not required | No GPU requirement documented. |
When to upgrade your hardware
Library growth
Processing load
Host memory pressure
Plan hardware growth with confidence
SSD config/database
Keep config, database, cache, and metadata on SSD.
SSDMore RAM
Useful when several media tools share one host.
Higher-RAM hostLarge library pool
Use multi-bay storage for media and backups.
ZimaCube-class storageStronger CPU
Helpful for conversion and metadata processing.
Higher-throughput CPUCan it run on ZimaOS?
Install LazyLibrarian from the ZimaOS App Store
A specific public LazyLibrarian App Store page is verified.
Open LazyLibrarian in the ZimaOS App Store ↗Follow upstream installation guidance
The project documents source installs and third-party Docker packages.
Open LazyLibrarian install docs ↗Keep library and config persistent
Do not place library or state in ephemeral container storage.
Open LazyLibrarian repository ↗Zima hardware for LazyLibrarian
LazyLibrarian itself is light; the retained media library and optional conversion/download stack usually determine the hardware tier.
Choose by workload
Use a low-power host with SSD config storage and separate media capacity.
Drive capacity and processing throughput become more important.
Zima product guidance is a practical workload mapping, not an upstream hardware certification.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and a 4-core N150 limit heavier CI, databases, and high-concurrency work | Get Now |
| ZimaCube 2 Standard | Storage-heavy libraries and large persistent data sets | Workloads where drive capacity matters more than maximum CPU throughput |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, and database-heavy workloads | Builds, indexing, many connections, or demanding containers |
|
16 GB RAM can still limit very large builds, databases, or local AI | 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 LazyLibrarian need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does LazyLibrarian need?
No numerical official CPU minimum is published.
Which Python version does LazyLibrarian require?
The current upstream README requires Python 3.7 or higher for source installs.
What port does LazyLibrarian use?
The default web UI port is 5299.
Does LazyLibrarian publish its own official Docker image?
The project documents third-party Docker packages such as LinuxServer; these should not be called first-party images.
Can ZimaBoard 2 832 run LazyLibrarian?
Yes for a small personal library with suitable attached storage.
Does LazyLibrarian need a GPU?
No GPU requirement is documented.
When should I choose ZimaCube 2?
When media retention, multi-drive capacity, or CPU-heavy conversion tools justify it.
