pastilhas
f23ec1283b
ported from the standalone officer-atelier service: providers (adapter-shaped, openai the only adapter today), the generation queue, collections, and the database layer — kept on its own Postgres database rather than folded into officer_db, since both collections and provider_settings had rows on the machine this was extracted from. what changed rather than just moved: - images are served from an authenticated GET /files/:filename instead of an unauthenticated PUBLIC_URL-prefixed static route - the OpenAI-key bootstrap fallback reads the secret store (getSecret) before .env, per-adapter - provider_settings (the one-row-per-adapter shape providers replaced) did not come along — it has no callers left anywhere in the server code, only a migration script that also did not move ping/echo (smoke-test routes with no caller) did not move either; the sidecar's own /_health covers liveness. not yet wired into the platform: sidecar/index.ts exists but nothing mounts it, and web/ has not been written, so this is not yet a discoverable plugin.
11 lines
639 B
TypeScript
11 lines
639 B
TypeScript
// What drizzle-kit creates, and the runtime's view of the tables — in the SEPARATE `atelier` database,
|
|
// not officer_db. See PLUGIN.md for why this plugin keeps its own database rather than folding into
|
|
// officer_db's <appname>_-prefixed convention: both `collections` and `provider_settings` had rows on
|
|
// the machine this was extracted from, and losing someone's generated images to a schema decision is
|
|
// not a trade to make unattended.
|
|
//
|
|
// `provider_settings` is deliberately not exported here — see ./index.ts.
|
|
export * from './generations/schema';
|
|
export * from './collections/schema';
|
|
export * from './providers/schema';
|