APTLY-PUBLISHER(1)

💅 NAME 💅

aptly-publisher — bestie, this is the tool for easy creation of Aptly multi component publishes ✨

---

🌸 DESCRIPTION 🌸

okay so here's the whole vibe. you run it like this:

usage: aptly-publisher [-h] [-v] [-d] [--dry] [--timeout TIMEOUT] --url URL [--recreate] [--no-recreate] [--force-overwrite] [--publish-contents] [--acquire-by-hash] [--components COMPONENTS [COMPONENTS ...]]  [--storage STORAGE] [-p PUBLISH [PUBLISH ...]] [-c CONFIG] [--dists DISTS [DISTS ...]]  [--architectures ARCHITECTURES [ARCHITECTURES ...]]  [--only-latest] [--source SOURCE] [--target TARGET] [--packages PACKAGES [PACKAGES ...]] [--diff] [--hard] [-r RESTORE_FILE] [-s SAVE_DIR] [-x PREFIX] action

🫶 positional arguments:

• action — the thing you actually wanna do. it's giving: publish, promote, cleanup, restore, dump, purge 👑

🎀 options:

• -h, --help — shows this help message and then dips, periodt

✨ Common:

• -v, --verbose — chatty mode, bestie
• -d, --debug — debug mode, for when you need to see everything
• --dry, --dry-run — pretend to do the thing, don't actually do the thing
• --timeout TIMEOUT — Aptly client timeout. bump it up for bigger publishes and slow servers, no cap 🐌
• --url URL — URL to Aptly API, eg. http://localhost:8080
• --recreate — drop the publish and create it again. literally the only way to add new components, iykyk
• --no-recreate — never recreate a publish (even when we're adding new components where that's, like, the only option 🙈)
• --force-overwrite — overwrite files in pool/ directory without notice. no warning, just vibes 💀
• --publish-contents — publish contents. it's slow so it's disabled by default, specifically so large repositories can survive 🐢
• --acquire-by-hash — use the Acquire-by-hash option. this may help with repository consistency ✨
• --components COMPONENTS [COMPONENTS ...] — space-separated list of components to promote or restore, or to purge (in case of purge)
• --storage STORAGE — storage backend to use for all publishes. can be empty (filesystem, the default), or swift:[name], or s3:[name] 🦋
• -p PUBLISH [PUBLISH ...], --publish PUBLISH [PUBLISH ...] — space-separated list of publish

🌈 Action 'publish':

• -c CONFIG, --config CONFIG — configuration YAML file
• --dists DISTS [DISTS ...] — space-separated list of distribution to work with (including prefix), default all.
• --architectures ARCHITECTURES [ARCHITECTURES ...] — list of architectures to publish (also determined by config, defaults to amd64, i386)
• --only-latest — publish only latest packages of every publishes

💜 Action 'promote':

• --source SOURCE — source publish to take snapshots from. can be a regular expression, eg. jessie(/?.*)/nightly
• --target TARGET — target publish to update. must be format if source is regex, eg. jessie{0}/testing
• --packages PACKAGES [PACKAGES ...] — space-separated list of packages to promote
• --diff — show differences between publishes (snapshots to be updated)

🔥 Purge:

• --hard — remove all unused packages and snapshots. yep, all of them 😭

🌸 Action 'restore':

• -r RESTORE_FILE, --restore-file RESTORE_FILE — file used to restore publish

⭐ Action 'dump':

• -s SAVE_DIR, --save-dir SAVE_DIR — path of where dump of publish will be done
• -x PREFIX, --prefix PREFIX — prefix for dump files' names

---

🧚 SEE ALSO 🧚

the full documentation for aptly-publisher is maintained as a Texinfo manual. if the info and aptly-publisher programs are properly installed at your site, the command

info aptly-publisher

should give you access to the complete manual. go off, bestie 🫶

---

💖 that's the whole page, mwah! this was aptly-publisher 0.12.12-1, dated October 2022. slay 💅✨