Download the *.uz file on a connected machine, verify its SHA‑256, then transfer it via USB or mounted drive to the offline server.
Because EAV lacks a fixed schema, the UZ package includes a eav_diff.json that describes:
The offline tool applies these changes directly to the system’s EAV tables without external validation. offline update eav uzsoft uz zip
Copy the extracted folder (the entire folder, not just the files inside) to your USB drive. Eject the USB drive safely and plug it into the offline computer (Server-Room-01). Copy the folder from the USB to a local directory (e.g., C:\temp\eav_upd).
A: Use uz-create-offline-bundle --source-install=/opt/uzsoft/eav --output custom_offline.uz.zip. This packages your current state and any staged patches. Useful for cloning configurations. Download the *
| Scenario | Recommendation |
|----------|----------------|
| Server with no internet (air-gapped) | ✅ Offline .uz.zip |
| Slow/unstable connection | ✅ Offline |
| Single test machine with good internet | Online (automatic) |
| Production cluster behind a proxy | Offline (safer) |
In environments where internet connectivity is intermittent, security-locked, or deliberately air‑gapped, performing system updates becomes a challenge. For users of UZsoft’s EAV (Entity‑Attribute‑Value) based platforms, offline updates are not just a fallback — they are a core operational requirement. The offline tool applies these changes directly to
This post explores the architecture, preparation, and execution of offline updates using the proprietary UZ‑formatted ZIP package.