Skip to content

Server file locations

See also: Client file locations.

Canvus Connect server organizes files across multiple folders. The files can be categorized as follows:

  • Configuration file: Canvus server configuration file is called mt-canvus-server.ini. The installer also provides a reference template alongside the working file.
  • Asset files: The asset files contain file-based content for canvases.
  • Log files: Canvus server writes a single server log file. The built-in web UI runs in-process and does not create a separate log.
  • License files: Canvus server requires a license file.
  • Session secret: The container keeps its generated web-client session secret inside the container, not on the /canvus-data volume. Set SESSION_SECRET to keep sessions across updates. See Web-client session secret.

Containerized deployments (26.4.0+)

The containerized Canvus server (Podman/Docker) stores all persistent state under a single host directory, by default /canvus-data/, which is bind-mounted into the canvus-combined and canvus-postgres containers. See Containerized layout (Podman/Docker) below for the full tree. The bare-metal paths documented in the rest of this page still apply to traditional installations on Ubuntu and Windows.

Configuration file

The configuration file for Canvus server is called mt-canvus-server.ini. The server installation also provides a reference template, mt-canvus-server.ini.template, that can be used as a starting point. (Legacy 3.x packages named this reference file mt-canvus-server.ini.example.)

Where is mt-canvus-server.ini on Ubuntu computers?

  • Working version: /etc/MultiTaction/canvus/mt-canvus-server.ini
  • Reference template: /etc/MultiTaction/canvus/mt-canvus-server.ini.template (legacy 3.x packages: mt-canvus-server.ini.example)

Where is mt-canvus-server.ini on Windows computers?

  • Working version: C:\ProgramData\MultiTaction\canvus\mt-canvus-server.ini
  • Reference template: %PROGRAMFILES%\MT Canvus Server\installer\mt-canvus-server.ini.template (legacy 3.x packages: C:\ProgramData\MultiTaction\canvus\mt-canvus-server.ini.example)

Asset files

The assets on canvases are stored in the asset folder. The default location depends on the operating system:

  • Ubuntu: /var/lib/mt-canvus-server/assets
  • Windows: C:\ProgramData\MultiTaction\canvus\assets

Where are the log files?

The Canvus server log files take the following file name format: mt-canvus-server-<date>.log. You can find the log files in the following folders:

  • Ubuntu: /var/lib/mt-canvus-server/logs/server/
  • Windows: C:\ProgramData\MultiTaction\canvus\logs\server\

The built-in web UI runs in-process and logs to this same server log; Canvus server does not write a separate dashboard log file. (Legacy 3.x packages wrote logs directly into logs/ rather than the logs/server/ subfolder.)

Where is my server license?

The location for an activated server license depends on the operating system:

  • Windows: Canvus server searches these folders for a license:
    • C:\Windows\System32\config\systemprofile\AppData\Local\MultiTaction\Licenses
    • C:\ProgramData\MultiTaction\Licenses
    • C:\Windows\System32\config\systemprofile\AppData\Roaming\MultiTouch\Licenses
  • Ubuntu: Canvus server searches these folders for a license:
    • /var/lib/mt-canvus-server/MultiTaction/Licenses
    • /etc/MultiTaction/Licenses
    • /var/lib/mt-canvus-server/.MultiTouch/Licenses

Where is Canvus server application binary?

The Canvus server application itself ([mt-canvus-server.exe]{.title-ref} on Windows and [mt-canvus-server]{.title-ref} on Ubuntu) can be found in the following locations:

  • Windows: %PROGRAMFILES%\MT Canvus Server\bin
  • Ubuntu: /opt/canvus/bin (legacy 3.x packages: /opt/mt-canvus-server/bin)

In the containerized deployment the binary ships inside the canvus-combined image at /opt/canvus/bin/mt-canvus-server; operators do not normally need to interact with it directly.

Containerized layout (Podman/Docker)

From 26.4.0, the supported deployment model is a two-container stack (canvus-combined and canvus-postgres) orchestrated with podman-compose or docker-compose. (A third service, canvus-media, for WebRTC video streaming is planned but not yet enabled, it is commented out in the compose file.) All persistent state lives under a single host directory, /canvus-data/ by default, which is bind-mounted into the containers.

/canvus-data/ directory contents

Under /canvus-data/:

  • assets/: canvas content (images, videos, PDFs, notes, etc.)
  • backups/: destination for manual server backups (nothing is written here automatically); backups/database/ is mounted into the canvus-postgres container as the location for database dumps
  • certs/: SSL certificate and key (mounted read-write in 26.4.0)
  • config/: working mt-canvus-server.ini
  • licenses/: activated license files
  • logs/: server logs (written to the logs/server/ subfolder)
  • postgres/: PostgreSQL data directory (owned by the canvus-postgres container)

The compose file maps each subdirectory to the path the container expects:

  • /canvus-data/assets → /var/lib/mt-canvus-server/assets (inside canvus-combined)
  • /canvus-data/backups → /var/lib/mt-canvus-server/backups
  • /canvus-data/certs → /etc/MultiTaction/canvus/server/certificates
  • /canvus-data/config → /etc/MultiTaction/canvus
  • /canvus-data/licenses → /var/lib/mt-canvus-server/MultiTaction/Licenses
  • /canvus-data/logs → /var/lib/mt-canvus-server/logs
  • /canvus-data/postgres → /var/lib/postgresql/data (inside canvus-postgres)

SFU media files (coming soon)

The canvus-media service (WebRTC video streaming) is not yet enabled. When it ships, it will read assets from the same /canvus-data/assets bind mount and adds no new host paths. Its HLS output is written under that shared assets directory at /canvus-data/assets/hls/<hash>/, so the transcoded segments are persistent on the host rather than ephemeral inside the container image.

Dashboard session secret

The container entrypoint uses SESSION_SECRET from the container environment if you set it. Otherwise it generates a secret on first start and keeps it inside the container, not on the /canvus-data volume, so it does not survive podman-compose down and up. Every update then signs all users out.

To keep sessions across updates, set SESSION_SECRET in podman-compose.yml to a long random value, for example the output of openssl rand -hex 32.

Treat the session secret as a secret

The session secret signs web-client session cookies. Keep it out of version control and support tickets, and keep a copy with your backups. See the Web-client session secret section of the configuration reference.