I'm currently using aptly to manage a local Debian repository hosted in S3. I've created a .deb for our aptly installation, bundling up the aptly.conf, repo/publish commands, cron tasks, etc.
If the system hosting aptly needed to be replaced, I'll simply install my aptly .deb on the new system, and hope/expect it to pick up from where things left off. So far, so good.
However, to make sure that the next aptly publish command does not remove packages from the S3 repository that are not in the new system, I'd like to "seed" the newly created local aptly repo with the contents of the repository in the S3 bucket. For this use case, using aptly mirror to create a local mirror of that S3 repository seems like the best fit; I can then import that local mirror into the local repo as the "seed".
The problem/requested feature is to have aptly mirror be able to mirror from S3-hosted repositories; this would be symmetrical with publishing to S3-hosted repositories.
I'm currently using
aptly
to manage a local Debian repository hosted in S3. I've created a.deb
for our aptly installation, bundling up theaptly.conf
, repo/publish commands, cron tasks, etc.If the system hosting
aptly
needed to be replaced, I'll simply install my aptly.deb
on the new system, and hope/expect it to pick up from where things left off. So far, so good.However, to make sure that the next
aptly publish
command does not remove packages from the S3 repository that are not in the new system, I'd like to "seed" the newly created local aptly repo with the contents of the repository in the S3 bucket. For this use case, usingaptly mirror
to create a local mirror of that S3 repository seems like the best fit; I can then import that local mirror into the local repo as the "seed".The problem/requested feature is to have
aptly mirror
be able to mirror from S3-hosted repositories; this would be symmetrical with publishing to S3-hosted repositories.Thanks!