Managing packages

Integration packages extend Plakar with connectors for cloud storage providers, databases, and other systems. This guide covers the full lifecycle of a package: installing, listing, upgrading, and removing.

List installed packages

To see which packages are currently installed:

$ plakar pkg list

Install a package

Pre-built package

Pre-built packages are hosted on Plakar’s infrastructure and require you to be logged in to download them. If you are not logged in, plakar pkg add will fail with an authentication error.

To log in:

$ plakar login

For CI pipelines or automated environments where interactive login is not possible, see Logging In to Plakar.

Once logged in, install a package by name from the official plugin registry (e.g. the S3 integration):

$ plakar pkg add s3

To install a specific version:

$ plakar pkg add s3@v1.0.0

Building from source

If you are not logged in or prefer not to use pre-built packages, you can build packages locally with plakar pkg build. This does not require a Plakar account but does require a working Go toolchain and make.

$ plakar pkg build s3

On success, a .ptar archive is generated in the current directory. Install it with:

$ plakar pkg add ./s3_v1.0.0_darwin_arm64.ptar

Upgrade a package

To upgrade a specific package to the latest available version:

$ plakar pkg add -u s3

To upgrade all installed packages at once:

$ plakar pkg add -u

Upgrading preserves existing store, source, and destination configurations.

Remove a package

$ plakar pkg rm s3