PLAKAR-STORE(1)

📦
version 1.1.7 · 2 versions
, in nixpkgs unstable

💾 PLAKAR-STORE(1) — the plakar-store girlies' guide

okay so this is the manual page for plakar-store, from the General Commands Manual section, and honestly? it's giving "i manage your storage configs so you don't have to" 💅 let's get into it bestie.

✨ NAME ✨

plakar-store — manage Plakar store configurations 🎀

🌸 SYNOPSIS 🌸

plakar store subcommand ...

💖 DESCRIPTION 💖

The plakar store command manages the Plakar store configurations, fr fr. 🗂️

The configuration is literally a set of named entries, and each one of them describes a Plakar store holding backups. no cap.

A store is defined by at least a location, which specifies the storage implementation to use, plus some storage-specific parameters. that's the whole vibe. ✨

The subcommands are as follows, bestie — pay attention, i'm not repeating myself (i will probably repeat myself):

  • add name location [option=value ...] — create a new store entry identified by name with the specified location. you can set specific additional configuration parameters by adding option=value parameters. slay. 🫶
  • check name — check whether the store identified by name is properly configured. vibe check for your config, basically. ✔️
  • import [-config location] [-overwrite] [-rclone] [sections ...] — import store configurations from various sources including files, piped input, or rclone configurations. 🧚

By default, it reads from stdin, allowing for piped input from other commands. iconic pipeline behaviour.

The -config option specifies a file or URL to read the configuration from.

The -overwrite option allows overwriting existing store configurations with the same names. (yes, it will absolutely clobber them, that's the point.)

The -rclone option treats the input as an rclone configuration, useful for importing rclone remotes as Plakar stores. so handy.

Specific sections can be imported by listing their names.

Sections can be renamed during import by appending :newname. yes, colon, then the new name. periodt.

For detailed examples and usage patterns, see the https://plakar.io/docs/v1.1.0/guides/importing-configurations/ Importing Configurations guide. 📚

  • ping name — try to connect to the store identified by name to make sure it is reachable. like a little "u up?" text but for storage. 📡
  • rm name — remove the store identified by name from the configuration. bye bestie 👋
  • set name [option=value ...] — set the option to value for the store identified by name. multiple option/value pairs can be specified. go off, set them all.
  • show [-secrets] [name ...] — display the current stores configuration. if -secrets is specified, sensitive information such as passwords or tokens will be shown. 🙈
⚠️ okay so -secrets literally prints your passwords and tokens. screen-share with care, bestie. 💀
  • unset name [option ...] — remove the option for the store entry identified by name. the opposite of set, obviously. 🦋

🌈 HTTP AND HTTPS STORE OPTIONS 🌈

When using an http:// or https:// location, the following additional options are available, and you're gonna want to know them:

  • auth_token — bearer token sent in the “Authorization” header for every request. 🔑
  • insecure — optional, set to true to opt-in the usage of the auth_token on HTTP plaintext connections. (yes that's exactly as spicy as it sounds. opt in on purpose.)
  • timeout — per-request timeout, default to "5m" i.e. five minutes. ⏱️
  • tls_no_verify — set to true to disable TLS certificate verification. useful when the server uses a self-signed certificate. 🔓

⭐ EXIT STATUS ⭐

The plakar-store utility exits 0 on success, and >0 if an error occurs. simple as that. 💫

👑 SEE ALSO 👑

and that's the whole page, bestie!! 🎀 written for Debian, dated September 2, 2026 — mwah, go configure some stores 💖✨🦋

📦 where this page comes from