feat(engine): the proton engine, and git in the proton image - #4
Merged
Merged
Conversation
engines/proton.yml moves a staging tree into one Proton Drive folder through the official CLI: the session pulled from the bucket and sealed back after every call, the destination checked by UID, one upload whose summary confirms it, hooks for the mirror's stage and prune. The bucket holds only the session: the CLI skips identical content and create-new-revision handles the rest, so Proton's version history is the mirror's history. The proton image gains git and s3, a boto3 get/put, and tells boto3 to send checksums only when required, which is R2's one quirk. examples/proton consumes the engine and its offline verb is the engine's check: confirm over an accepting and a refusing summary, and the age verb's round trip.
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
1 participant
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.
What
engines/proton.yml: the second engine. A staging tree into one Proton Drive folder through the official CLI:sessionpulls the age-encrypted session from the bucket, every CLI call goes throughpd, which seals the session back when its token rotated whatever the exit,destinationrefuses a folder whose UID is not the vault's,uploadis onefilesystem upload -f create-new-revision -d merge -t --json,confirmreads the summary,stageandpruneare the mirror's hooks. No state of the mirror's in the bucket: the CLI skips identical content, so Proton's version history is the history.git,s3(a boto3 get/put at/usr/local/bin/s3), and two ENV lines that make boto3 send checksums only when required.examples/protonconsumes the engine; itsofflineverb is the engine's check andci.ymlruns it for both variants.toolbox.yml.Additive:
toolbox.ymlandengines/rsync.ymlchange in comments only, so ctan, tlnet and dropbox render the same. Dropbox pulls a rebuiltproton-v2with git in it after the release.Test plan
examples/proton:task image-build,task run -- task tools,task run -- task offline,task checkall pass locally on Apple containerexamples/rsync:task checkunchangedv2.1.0; the first katoptra/github run is the live check