Skip to Content
XiotBox Documentation

Before you begin

Collect every prerequisite before changing Odoo or a desktop computer.

Odoo 19.0 & 18.0 supported
This guide assumes Odoo is already running. XiotBox does not install or provide Odoo or VentorTech Direct Print PRO (printnode_base); both must already be in place and licensed before you start. If either is missing, stop and obtain it first — there is nothing to deploy until the Odoo module can be installed.

What you need

□ Odoo 19 or Odoo 18 Community or Enterprise where custom modules can be installed.

□ A legally obtained printnode_base build matching the same Odoo major version (VentorTech Odoo Direct Print PRO — Odoo 19 or Odoo 18). It is not included with XiotBox and must be purchased separately.

□ The matching Odoo 19 or 18 xiotbox_lite module obtained from a registered order, plus a registered Customer Downloads account.

□ A Docker-capable x86-64 host for the compiled Runtime + embedded SocketD service. A separate Linux host is mandatory for Odoo.sh and recommended for public production.

□ One test computer, one printer and the supported official PrintNode desktop client.

□ Administrator access to Odoo, DNS and the Runtime host.

Recommended production baseline

Runtime hostUbuntu 22.04/24.04 LTS, 2 vCPU, 4 GB RAM, 20 GB free disk
Domainsruntime.example.com and socketd.example.com
IngressTCP 443 from desktop networks; SSH restricted to administrators
EgressHTTPS from Odoo to Runtime and from Runtime to Odoo
TLSA valid public certificate whose hostname matches each public URL
Do not continue without a backup. Back up the database and filestore together. If migrating an existing account, also record its current endpoint and keep the official desktop installer.
Planning: with Odoo and printnode_base already in place, allow 1–2 hours for the first deployment, plus a separate maintenance window for a migration.

Choose a maintenance window

A fresh installation can normally be prepared without interrupting users. For a migration, stop automated printing while endpoints and printers are being mapped. Keep the former PrintNode subscription active until the acceptance print succeeds.