Skip to content

CLI

The container image ships an xique console script for operator tasks. In the quadlet deployment it runs inside one of the pod's containers:

podman exec xique-web xique --help

import-trakt

Validate a Trakt export zip and queue its import as a worker job:

podman exec xique-web xique import-trakt /data/imports-temp/export.zip --user marvin8
  • zip_path — path to the Trakt export zip. The file is never deleted by the CLI path; keep the export wherever you manage your own archives.
  • --user — username to import for. Optional when the instance has exactly one user; with more, the command fails and lists the existing usernames so you can disambiguate.

The command validates the archive locally and records a trakt_import job; the worker does the actual parsing on its next cycle. Watch progress in the worker log:

journalctl --user -u xique-worker -f

!!! note "The usual route is the web UI"

The same import is available in **Settings → Trakt import**, where the
upload streams into the shared imports volume and is deleted after a
successful parse. The CLI path exists for bootstrapping a fresh instance
before the UI is convenient, and for scripting.

Getting the zip into the container

The CLI reads a path visible inside the container. Either copy the export into the shared imports volume first:

podman cp export.zip xique-web:/data/imports-temp/export.zip

or bind-mount a host directory into the unit and reference it there.