PLAKAR-DESTINATION(1)

💅 PLAKAR-DESTINATION 💅

okay so bestie, this is the plakar-destination page from the General Commands Manual, and it's genuinely the glow-up your restore game has been waiting for. Let's get into it ✨

---

🌸 NAME 🌸

plakar-destination — the whole vibe of managing your Plakar restore destination configuration 🎀

---

🦋 SYNOPSIS 🦋

plakar destination subcommand ...

---

✨ DESCRIPTION ✨

So the plakar destination command handles the configuration of destinations — like, the places where Plakar will actually restore stuff. That's the whole point. 💖

The configuration is a set of named entries, and each one describes a destination where a restore operation may happen. Think of it like a little contact list of places your backups can go live. 👑

A destination is defined by at least a location, which tells you which exporter to use, plus some exporter-specific parameters. That's the bare minimum, fr fr.

The subcommands are as follows:

• add _name_ _location_ [_option=value_ ...] — creates a brand-new destination entry identified by _name_, with the _location_ you give describing the exporter to use. Want extra exporter options? Just tack on more option=value parameters. iconic behavior.
• check _name_ — checks whether the exporter for the destination identified by _name_ is properly configured. a lil vibe check for your config 🔍
• import [-config _location_] [-overwrite] [-rclone] [_sections_ ...] — imports destination configurations from various sources: files, piped input, or rclone configurations. slay.
  • By default it reads from stdin, which means you can pipe input in from other commands like plakar source show. love that for you 🫶
  • The -config option specifies a file or URL to read the configuration from.
  • The -overwrite option allows overwriting existing destination configurations with the same names. (yes, it will absolutely replace them, be aware 💀)
  • The -rclone option treats the input as an rclone configuration — super useful for importing rclone remotes as Plakar destinations.
  • Specific sections can be imported by listing their names.
  • Sections can be renamed during import by appending :newname.
  • For detailed examples and usage patterns, see the https://plakar.io/docs/v1.1.0/guides/importing-configurations/ Importing Configurations guide. go read it, iykyk 📖
• ping _name_ — tries to open the destination identified by _name_ just to make sure it's reachable. like a "u up?" text but for infrastructure 💌
• rm _name_ — removes the destination identified by _name_ from the configuration. bye bestie 👋
• set _name_ [_option=value_ ...] — sets the option to value for the destination identified by _name_. You can specify multiple option/value pairs at once. efficiency queen 👑
• show [-secrets] [_name_ ...] — displays the current destinations configuration. If -secrets is specified, sensitive information such as passwords or tokens will be shown. ⚠️ like, actually sensitive, so maybe don't do that in a screen share 🙈
• unset _name_ [_option_ ...] — removes the option for the destination entry identified by _name_.

---

🔥 EXIT STATUS 🔥

The plakar-destination utility exits 0 on success, and >0 if an error occurs. simple as that, periodt. ⭐

---

🌈 SEE ALSO 🌈

• plakar(1)

---

and that's the whole page bestie!! 🍓 this one's from Debian, dated September 11, 2025 — go forth and configure your destinations, you absolute main character 🧚💜