Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support for Mirroring Debian Repositories with S3 #1432

Open
marmik18 opened this issue Feb 18, 2025 · 2 comments
Open

Feature Request: Support for Mirroring Debian Repositories with S3 #1432

marmik18 opened this issue Feb 18, 2025 · 2 comments
Labels

Comments

@marmik18
Copy link

marmik18 commented Feb 18, 2025

Hey,

Thank you all for maintaining such a great project! I have a feature request regarding repository mirroring in Aptly.

Current Situation:

Aptly currently supports mirroring Debian repositories that are exported via HTTP(S) or FTP. Since Aptly already supports publishing repositories to S3, I believe it should also support mirroring repositories hosted on S3.

What I am Trying to Achieve:

I am setting up a private repository for Debian packages on S3, where all package versions are stored.

  • I successfully created a repository, took a snapshot, and published it to an S3 bucket.
  • On the client side, I can install packages using apt-transport-s3.

The Problem:

Since I am building my packages in a CI/CD pipeline, I need a way to:

  • Pull all the existing packages from my S3 repository.
  • Build a new version of the package.
  • Create a new repository with the updated .deb files.
  • Take a snapshot and publish it.

Currently, Aptly does not support mirroring repositories stored on S3, which makes it difficult to fetch and manage package versions efficiently.

Request:

Would it be possible to add support for mirroring Debian repositories hosted on S3 in Aptly?

I am relatively new to Debian repositories, so please correct me if I am misunderstanding something.

Thank you in advance! 😊

@neolynx
Copy link
Member

neolynx commented Feb 22, 2025

Hi !

good idea :-) Duplicate of #455 (comment) ?

one other way could be: #843

I would start hosting the pool in S3, like #1074 and then centralize the db (i.e. like Azure Cosmos DB as suggested in #230, but for aws).

This would avoid downloading your packages first, and s3 pool is used directly.

What do you think ?

@marmik18
Copy link
Author

That makes sense, I could push the directory ~/.aptly to s3 and then sync them with every container to keep the state synced.

Is my understanding correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants