.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.5.
.TH APTLY-PUBLISHER "1" "January 2018" "aptly-publisher 0.12.10-1" "User Commands"
.SH NAME
aptly-publisher \- tool for easy creation of Aptly multi component publishes
.SH DESCRIPTION
usage: aptly\-publisher [\-h] [\-v] [\-d] [\-\-dry] [\-\-timeout TIMEOUT] \fB\-\-url\fR URL
.TP
[\-\-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
.SS "positional arguments:"
.TP
action
Action to perform (publish, promote, cleanup, restore,
dump, purge)
.SS "optional arguments:"
.TP
\fB\-h\fR, \fB\-\-help\fR
show this help message and exit
.SS "Common:"
.HP
\fB\-v\fR, \fB\-\-verbose\fR
.HP
\fB\-d\fR, \fB\-\-debug\fR
.HP
\fB\-\-dry\fR, \fB\-\-dry\-run\fR
.TP
\fB\-\-timeout\fR TIMEOUT
Aptly client timeout. Raise for larger publishes and
slow server.
.TP
\fB\-\-url\fR URL
URL to Aptly API, eg. http://localhost:8080
.TP
\fB\-\-recreate\fR
Drop publish and create it again, only way to add new
components
.TP
\fB\-\-no\-recreate\fR
Never recreate publish (even when we are adding new
components where it's the only option)
.TP
\fB\-\-force\-overwrite\fR
Overwrite files in pool/ directory without notice
.TP
\fB\-\-publish\-contents\fR
Publish contents. It's slow so disabled by default to
support large repositories.
.TP
\fB\-\-acquire\-by\-hash\fR
Use Acquire\-by\-hash option. This may help with
repository consistency.
.TP
\fB\-\-components\fR COMPONENTS [COMPONENTS ...]
Space\-separated list of components to promote or
restore or to purge (in case of purge)
.TP
\fB\-\-storage\fR STORAGE
Storage backend to use for all publishes, can be empty
(filesystem, default), swift:[name] or s3:[name]
.TP
\fB\-p\fR PUBLISH [PUBLISH ...], \fB\-\-publish\fR PUBLISH [PUBLISH ...]
Space\-separated list of publish
.SS "Action 'publish':"
.TP
\fB\-c\fR CONFIG, \fB\-\-config\fR CONFIG
Configuration YAML file
.TP
\fB\-\-dists\fR DISTS [DISTS ...]
Space\-separated list of distribution to work with
(including prefix), default all.
.TP
\fB\-\-architectures\fR ARCHITECTURES [ARCHITECTURES ...]
List of architectures to publish (also determined by
config, defaults to amd64, i386)
.TP
\fB\-\-only\-latest\fR
Publish only latest packages of every publishes
.SS "Action 'promote':"
.TP
\fB\-\-source\fR SOURCE
Source publish to take snapshots from. Can be regular
expression, eg. jessie(/?.*)/nightly
.TP
\fB\-\-target\fR TARGET
Target publish to update. Must be format if source is
regex, eg. jessie{0}/testing
.TP
\fB\-\-packages\fR PACKAGES [PACKAGES ...]
Space\-separated list of packages to promote
.TP
\fB\-\-diff\fR
Show differences between publishes (snapshots to be
updated)
.SS "Purge:"
.TP
\fB\-\-hard\fR
Remove all unused packages and snapshots
.SS "Action 'restore':"
.TP
\fB\-r\fR RESTORE_FILE, \fB\-\-restore\-file\fR RESTORE_FILE
File used to restore publish
.SS "Action 'dump':"
.TP
\fB\-s\fR SAVE_DIR, \fB\-\-save\-dir\fR SAVE_DIR
Path of where dump of publish will be done
.TP
\fB\-x\fR PREFIX, \fB\-\-prefix\fR PREFIX
Prefix for dump files' names
.SH "SEE ALSO"
The full documentation for
.B aptly-publisher
is maintained as a Texinfo manual.  If the
.B info
and
.B aptly-publisher
programs are properly installed at your site, the command
.IP
.B info aptly-publisher
.PP
should give you access to the complete manual.