adopt 0.4's persistent key store and browser setup form
The earlier bump took 0.4.1 for its model catalog and status page but
left PPQ_DATA_DIR unset, which disabled the key form the release exists
to add. Enable it, and let the proxy own the key outright.
PPQ_API_KEY is no longer passed. The volume's `proxy/` subpath mounts at
/data as PPQ_DATA_DIR, so upstream's key store is the single source of
truth: the Status Page and the Configure PPQ API Key action write the
same config.json, and there is no StartOS-side copy to revert what the
browser saved. A chown oneshot hands /data to the image's `node` user so
the page can write there.
Verbose Logging moves to store.json outside the mount, because upstream
rewrites config.json wholesale when a key is saved and would drop it.
main.ts watches config.json — upstream loads it once at startup, so the
watch is what makes the action take effect: the write restarts the
daemon, which reloads the file. A key saved on the page applies
immediately and converges through the same restart.
The task drops from critical to important. A critical task suspends
every other control, so it would have left the user unable to start the
service and reach the page's own form — and with PPQ_DATA_DIR set the
proxy no longer exits keyless; it attests, serves the page, and answers
401 until a key exists. main.ts clears the task when a key appears,
since saving on the page never touches the action that would clear it.
The action's key field is now validated against upstream's own
^sk-[A-Za-z0-9]{16,64}$ shape and no longer refuses a blank submission,
a key having become optional.
This commit is contained in:
10 files changed
+213
-140
No files matched your search
@@ -13,14 +13,14 @@ const dict = {
|
||||
'Point any OpenAI or Anthropic SDK client at this URL to use PPQ private (TEE) models with end-to-end encryption': 7,
|
||||
// actions/configureApiKey.ts
|
||||
'PPQ.AI API Key': 8,
|
||||
'Your API key from ppq.ai (Settings → API Keys). Leave blank to keep the key already saved.': 9,
|
||||
'Verbose Logging': 10,
|
||||
'Log every request the proxy handles. Useful for troubleshooting.': 11,
|
||||
'Configure PPQ API Key': 12,
|
||||
'Set the PPQ.AI API key the proxy uses to authenticate. Requests are billed to this key.': 13,
|
||||
'An API key is required. Create one at ppq.ai under Settings → API Keys.': 14,
|
||||
'Your API key from ppq.ai (Settings → API Keys). Leave blank to keep the key already saved, or to set one later from the Status Page.': 9,
|
||||
'A PPQ.AI key starts with "sk-".': 10,
|
||||
'Verbose Logging': 11,
|
||||
'Log every request the proxy handles. Useful for troubleshooting.': 12,
|
||||
'Configure PPQ API Key': 13,
|
||||
'Set the PPQ.AI API key the proxy uses to authenticate. Requests are billed to this key.': 14,
|
||||
// init/taskConfigureApiKey.ts
|
||||
'Add your PPQ.AI API key to start the proxy': 15,
|
||||
'Add your PPQ.AI API key here, or start the service and save one on the Status Page': 15,
|
||||
} as const
|
||||
|
||||
/**
|
||||
|
||||
Reference in new issue
Block a user