ONLYOFFICE Workspace Worked, but Not as a One-Click App
The thread began as a request to add tools such as dig and package ONLYOFFICE Workspace for the ZimaOS App Store. A community member then tested the platform and confirmed that the core Workspace stack could run, while emphasizing that its installer coordinates several services rather than deploying one simple container.
The platform can combine browser-based document editing, file storage, user roles, projects, CRM, calendar features, and optional mail. That breadth also explains why a generic install script can collide with an appliance-style host.
Storage Checks Could Target the Wrong Disk
The installer checked free space on the system disk by default. On a ZimaOS machine with a small operating-system device and a larger data pool, this could fail even when adequate capacity existed elsewhere. The thread's initial workaround changed the installer's base directory before running the Workspace installation.
This path must be adapted to the actual machine. Writing a large multi-container platform to the OS partition can fill the system drive, while copying a path from another user's machine can point to storage that does not exist.
Ports and Database Initialization Needed Manual Attention
Ports 80 and 443 were identified as likely conflicts because ZimaOS routing or other apps may already use them. The installation therefore needed a deliberate external port choice rather than assuming a clean Debian host.
Database initialization was also described as fragile. Incorrect quotation marks or mismatched variables could prevent authentication and make an almost-complete stack appear broken. The thread does not provide a single final Compose file whose behavior was independently verified across different ZimaOS storage layouts.
The Optional Mail Module Was the Hardest Boundary
The author wanted the mail installer to validate domain A and MX records, but the host lacked expected DNS utilities and other traditional Linux components. A reply noted that dig and nslookup are normally supplied by a DNS utilities package, while ZimaOS is not designed around installing arbitrary host packages.
The author eventually separated the problem: run ONLYOFFICE Workspace for collaboration and use a container-oriented mail platform instead of forcing the bundled mail module. They published experiments through their community Docker Hub repositories and later shared their related GitHub work.
Mail remained described as flaky, and later comments mentioned a different free mail product as working in one environment. These are community experiments, not an official ZimaOS mail-stack recommendation.
Why an App Store Package Was Requested
A native catalog package could predefine writable DATA paths, expose safe port choices, and remove installer checks that assume a conventional Linux distribution. That request remained a feature proposal in the thread; no IceWhale reply confirmed that an official ONLYOFFICE Workspace app was scheduled.
Security and Exposure Remain Separate Decisions
A working local deployment does not automatically provide safe internet access. The discussion mentioned LAN-only operation, HTTPS, reverse proxies, tunnels, audit logging, and authentication features, but did not validate one complete public-facing configuration. Operators should treat deployment, mail delivery, DNS, and external exposure as separate projects.
FAQ
Can ONLYOFFICE Workspace run on ZimaOS?
Community testing said the core Workspace stack could run, but it required path, port, and service adjustments and was not equivalent to installing a normal one-click app.
Why did the mail component fail?
It expected DNS utilities and other host-level behavior that the minimal ZimaOS environment did not provide. The user moved toward a separate containerized mail stack.
Was an official App Store package released in this thread?
No. Packaging Workspace for the store was a request, not a confirmed release commitment.
