szinck

3 ms·

1. 1.▲
   by szinck 10y ago

   Thanks! And thanks everyone else for all the comments!
2. 2.▲
   by szinck 10y ago

   I use it for "small"ish repos. Mainly I don't want to maintain a copy on disk. I have a list of (and tooling around) what all .debs go in a release, and copy from a master S3 location to the correct apt repo s3 location, a
3. 3.▲
   by szinck 10y ago

   Yeah you just sign the packages. There is an option to create a signed "Release" file, but I'm not creating a "Release" file. "Packages" is the only one I'm creating for now. If you wanted to creat
4. 4.▲
   by szinck 10y ago

   True, lambda setup is not super simple. However with deb-s3 you have to have a local copy of the .deb, whereas with what I'm doing the files never leave S3.
5. 5.▲
   by szinck 10y ago

   Oh cool. The only reason I chose apt-transport-s3 was that it was included in Ubuntu 16.10. It also only uses stuff from the standard python library so there's less bootstrapping before it is usable. That does look really cool though