celforyon/aptly repository overview

⁠Documentation

⁠Environment variables

⁠Installation and usage

⁠Preparation

Required files in ${webdir}:

• private.key containing your private GPG key
• passphrase containing the passphrase (so it is non-interactive)

⁠Launch

docker run --name aptly -d -e GPGKEY="${KEY}" -v "${webdir}":/opt/aptly -v "${shareddir}":/shared celforyon/aptly

⁠Create repository

docker exec aptly repo create "${dist}"

⁠Publishing

tmp=$(mktemp -dp "${shareddir})
mkdir "${tmp}/${dist}"
cp "${debfile} "${tmp}/${dist}/"

The debfile and two directories will be removed The subdirectory ${dist} must be a valid repository name The temporary directory is required but you can name it otherwise

⁠Serving

To serve your published packages, you need to run a web server on ${webdir}/public

⁠Available scripts

You can make use of these scripts by doing: docker exec aptly *script*

⁠init

It loads all repo and packages from the debs directory

⁠publish

Automatically pass passphrase for required subcommands.

⁠purge

It deletes all aptly generated data. Also, the debs archive of added packages is backuped in backup/debs.$(date '+%Y%m%d%s')

⁠list

⁠snapshot

⁠switch

⁠repo

⁠add

⁠create

It allows to create an aptly repository and is the same as: aptly repo create -distribution="${dist}" -component=main "${dist}"

⁠list

⁠snapshot

⁠create