deb-s3

I use deb-s3[1] which is sort of like this, but handles uploading the package and updating the Packages index in a single step. deb-s3 can also sign your Release file so apt won't complain about unsigned packages. The post mentioned deb-s3 and dismissed it as more complicated to setup than this solution. While the lambda solution is neat, I'm not sure I would describe it as simple. For now I think I'll stick with deb-s3. [1]: https://github.com/krobertson/deb-s3

This looks great. I've been using deb-s3 but it's a pain to setup ruby. https://github.com/krobertson/deb-s3

Similar to https://github.com/krobertson/deb-s3, however, it uses S3 metadata for each object to regenerate the indices.

We use deb-s3[1] to maintain a custom apt repository in s3. It supports signed release files and does all the hard work for you. [1]: https://github.com/krobertson/deb-s3

Yes, it requires some configuration though. On the S3 side there is a Ruby gem that will send .deb's up to a bucket and put the right files in the right places.[1] On the client side, apt-s3[2] provides the functionality for aptitude to download packages from S3 (Remember that S3 doesn't use normal HTTP basic so if you don't want your package public it needs to speak Amazon's language). A few people improved on this, and I have a straightforward fork and PPA built for this.[3] I've been using all this in production for a few months and it has worked wonderfully. Jenkins builds the package and sends it up via deb-s3 and app servers have chef scripts that stop/start the daemon and update the package. [1]https://github.com/krobertson/deb-s3 [2]https://github.com/kyleshank/apt-s3 [3]https://launchpad.net/~skye-book/+archive/apt-transport-s3