Server installation
This section describes how to install Canvus Server for the first time. If you are updating an existing installation, see updating.
Canvus Server has two current installation methods. Neither is a fallback for the other, and both receive the same releases.
- Standalone --- a native installer (
.debor MSI) that bundles the server, a dedicated PostgreSQL 18 cluster, and the web client, and runs them as native services. - Container --- Podman or Docker images, driven by a compose file.
Choosing an installation method
| Your situation | Suggested method |
|---|---|
| A single server, no container runtime installed | Standalone |
| You already run Podman or Docker and want Canvus inside it | Container |
| Windows Server estate managed with MSIs and Group Policy | Standalone |
| Adding a container runtime needs separate approval | Standalone |
| Air-gapped or tightly firewalled host | Standalone |
| You want one deployment pattern across Linux, Windows and macOS | Container |
| Evaluating on macOS | Container |
Both methods use the same server, the same database engine and the same data formats. The difference is how the software is packaged and how you operate it: standalone installs are managed with your operating system's own service and package tooling, container installs with your container tooling.
Upgrades differ, so read the procedure for your method before upgrading: standalone or container.
Legacy installations
Pages for Canvus 3.x and earlier, covering the Ubuntu 16.04 / 18.04 .deb and
the pre-26.4 Windows installer, are kept under Legacy in this section for
existing deployments. They are not a current installation method --- use
standalone or container for anything new.
To move an existing legacy installation onto containers, see migrating to containers.