feat: add filesystem snapshots and readonly zip mounts#47
Closed
ivarvong wants to merge 4 commits into
Closed
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FpxHS5iGm9ktgpnL9QZu9x
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.
Adds two filesystem capabilities on top of the VFS-backed JustBash filesystem.
Summary
JustBash.FS.to_tree/2to snapshot regular files under a root into a%{path => content}tree.JustBash.FS.Zip, an eager read-onlyVFS.Mountablebackend for ZIP archives.from_binary/2andfrom_url/3ZIP construction, with URL fetches going throughJustBash.Networkand the configured HTTP client.chmodfail with:erofs.Verification
mix test test/just_bash/fs_zip_test.exsmix testmix compile --warnings-as-errorsmix credohttps://fieldvault.2fsk.com/zip_mount_demo.zipNotes
JustBash.FS.Zip.from_url/3enforces archive limits before decompression, after the configured HTTP client returns the response body. A future streaming HTTP client path could enforce:max_archive_bytesbefore materializing remote response bytes.