We developed a tiny service to publish tarballs from a S3 (compatible) bucket in a format that is digestible as a Flake input (or channel). It’s pretty barebones, but it does implement the Lockable Tarball Protocol and supports authentication via JWT.
8 Likes
I’m a beginner to Cloud, DevOps and Nix. Can anyone tell me what’s the advantage of this?
Also a doubt, can this do:
Custom inputs for organisations where their employees can only install the packages whitelisted?
If so a separate repo for it is better than a tarball right?
Couldn’t get the potential possibilities of this 
.
Author or anyone else clarify me
I assume this is the foundation for channel update delivery for their upcoming LTS product based on NixOS.
1 Like
Hi @ksvivek! These are fair questions! We use this to ship channel updates (tarballs) from an internal Git repo. Shipping tarballs directly from our Git repo proved difficult with the limited authentication options that Nix supports, so we ended up with this solution. Maybe it’s helpful for someone else as well.
1 Like