Community-registry audit ahead of listing. Upstream 0.4.1 renames the model catalog (private/kimi-k2-6 → private/kimi-k3, drops qwen3-vl-30b) and serves a status page at GET /, so the package was documenting a stale model list and hiding a whole surface. Export that page as a `ui` interface alongside the existing `api` on one host, and unmask the API interface — its URL carries no credentials, so masking hid the address for nothing. PPQ_DATA_DIR stays unset deliberately. With it set, upstream persists a browser-entered key to its own config.json while the StartOS-supplied PPQ_API_KEY still wins at every restart, silently reverting the user. StartOS owns the key via the action; the status page's form renders disabled. CI never ran: build.yml's PR target and tagAndRelease.yml's push trigger both named `master` on a repo whose only branch is `main`. Point them at `main` and reset all three workflows to the package template, dropping the guard job retired in start-technologies@ed0dca2. packageRepo now names the Start9-Community fork, which is where CI runs, where the org's registry variables live, and where releases are cut. Also: drop three .catch handlers on file-model reads, which swallowed a genuine read failure into "no key configured" — readOnce already returns null for a missing file; pass null rather than an empty Mounts for the unmounted subcontainer; inline two single-use interface consts; and rewrite README/instructions against the writing guides, fixing a YAML block that claimed a /data mount the package deliberately does not make.
50 lines
1.6 KiB
TypeScript
50 lines
1.6 KiB
TypeScript
import { i18n } from './i18n'
|
|
import { sdk } from './sdk'
|
|
import { apiPort } from './utils'
|
|
import { configJson } from './fileModels/config.json'
|
|
|
|
export const main = sdk.setupMain(async ({ effects }) => {
|
|
console.info(i18n('Starting PPQ Private Mode!'))
|
|
|
|
// Read reactively so the daemon restarts when the user changes settings.
|
|
const apiKey = await configJson.read((c) => c.apiKey).const(effects)
|
|
const debug = await configJson.read((c) => c.debug).const(effects)
|
|
|
|
return sdk.Daemons.of(effects).addDaemon('proxy', {
|
|
// The proxy is stateless and fully configured via env — the 'main' volume
|
|
// (config.json, read host-side by the SDK) is never mounted into the
|
|
// container.
|
|
subcontainer: sdk.SubContainer.of(
|
|
effects,
|
|
{ imageId: 'proxy' },
|
|
null,
|
|
'proxy-sub',
|
|
),
|
|
exec: {
|
|
command: ['node', '/app/dist/bin/server.js'],
|
|
env: {
|
|
PPQ_API_KEY: apiKey ?? '',
|
|
HOST: '0.0.0.0',
|
|
PORT: apiPort.toString(),
|
|
DEBUG: debug ? 'true' : 'false',
|
|
},
|
|
},
|
|
// The proxy only binds its port after remote attestation of the enclave
|
|
// succeeds, so a listening port means the encrypted channel is verified
|
|
// and ready.
|
|
ready: {
|
|
display: i18n('Encrypted Proxy'),
|
|
fn: () =>
|
|
sdk.healthCheck.checkPortListening(effects, apiPort, {
|
|
successMessage: i18n(
|
|
'The proxy is ready — enclave attestation verified',
|
|
),
|
|
errorMessage: i18n(
|
|
'The proxy is not ready (enclave attestation pending)',
|
|
),
|
|
}),
|
|
},
|
|
requires: [],
|
|
})
|
|
})
|