Repository navigation
Source Vault: password-only (one Netlify setting for stems) - #51
Merged
Merged
Conversation
- Prompts, lyrics and analysis are locked with the access key itself (PBKDF2 → AES-256-GCM) in public/vault/data.enc.json and opened in the browser; no server sign-in - One function, vault-stems.mjs, hands out signed links from the private repo to visitors who prove they know the key; needs only VAULT_GH_TOKEN - Removes vault-unlock/lock/data/stem functions and the VAULT_KEY/SECRET/DATA_KEY settings Co-Authored-By: Claude Opus 5.5 <[email protected]>
✅ Deploy Preview for stirring-hamster-57bba9 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Follow-up to #50, which merged before this change landed. The live vault currently shows VAULT OFFLINE because it expects six Netlify settings. After this merges, the vault works with just the password.
What changes
public/vault/data.enc.json, and the browser opens them when the right key is typed. No server sign-in, and noVAULT_KEY/VAULT_SECRET/VAULT_DATA_KEYsettings.vault-stems.mjs, hands out GitHub's short-lived signed links from the private repoerror404website/error404-vault(release stems, created, currently empty). It only does this for visitors who prove they know the key, and only for allow-listed file names.vault-unlock,vault-lock,vault-dataandvault-stemfunctions.The one Netlify setting (for stems only)
VAULT_GH_TOKEN: a fine-grained GitHub token with access to error404-vault only, Contents: Read-only. Without it, everything works and stems show "SOON".Tested
npm run checkpasses.🤖 Generated with Claude Code