docs: persistent-demo walkthrough + SECURITY.md#5
Open
amiller wants to merge 2 commits into
Open
Conversation
Covers the dstack LUKS2 disk-encryption model, HKDF key derivation tied to app_id + instance_id, what lives in each SQLite table, token lifecycle, and Stage 0 limitations. README now points readers there and corrects the env-template filename. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Case study of why one permit stayed live for weeks while 41 siblings went stale. Covers the five decoupled ingredients (immutable capability code, year-long bearer, out-of-band cookie refresh, static GitHub Pages UI, untouched enclave), the DB evidence for the cookie-refresh correlation, a clone-this-pattern recipe, and the sidecar SSH debug checklist. Flags the unbuilt distribution path for the companion Chrome extension as an open question. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Two doc-only commits cherry-picked from #3 so they land on
mainwithout waiting on the broader custom-plugin discussion.docs/persistent-demo-walkthrough.md— case study of whyyt-shorts-v3stayed live for weeks while 41 sibling permits on the same enclave went stale within days. Covers the five decoupled ingredients (immutable capability code, year-long bearer, out-of-band cookie refresh via Chrome extension, static GitHub Pages UI, untouched dstack), the DB evidence for the cookie-refresh correlation, a clone-this-pattern recipe, and a sidecar-SSH debug checklist. Flags the unbuilt Web Store distribution path as an open question.SECURITY.md— dstack LUKS2 disk-encryption model, HKDF key derivation tied to app_id + instance_id, what lives in each SQLite table, token lifecycle, and Stage 0 limitations. README points here.Why this split
Both commits exist on
feat/custom-plugins-invoke(#3), but that PR is carrying a larger conceptual change (thecustomplugin type, /invoke endpoint, browser service) that wants teammate discussion before merging. These two docs are independent of that question and useful as a public reference right now — in particular, the walkthrough is the artifact I want to link from upcoming writing.Test plan
main'sproxy/src/server.tsand related files (the code paths they reference —/cookies/upload, secret re-resolution in/invoke, etc. — are onfeat/custom-plugins-invoke, not yet on main; links will resolve once Custom capability plugins + /invoke endpoint #3 merges, and in the meantime the doc is still self-contained)