feat(s3): Introduce S3 compatibility - #29
Merged
Merged
Conversation
SirBerg
marked this pull request as ready for review
July 7, 2026 15:05
Svenum
requested changes
Jul 7, 2026
…are actually available
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This PR introduces S3 storage backend support and the appropritate configuration options for it. Although I've verified it works it should be treated as an Alpha release and not stable.
How to test
Download the branch, run docker-compose up -d and verify that your storage_type in config.toml is set to "s3" and that you have set appropriate values in
[storage.s3](depending on how you've configured minio).This is something sensible that worked for the current dev setup:
After you've verified all that, run
bun cache::devand push to the cache like you normaly would, everything should work transparently to the cachix client.