feat(modaka-studio): recipe with its PostgreSQL and optional OpenID Connect sign-in #14

Merged
crapougnax merged 2 commits from feat/13-modaka-studio-recipe into develop 2026-11-16 20:11:03 +00:00
Member

Closes #13

What

New recipe modaka-studio: Modaka Studio with its own PostgreSQL, behind Traefik with a cert-manager certificate.

  • Two database roles. studio_owner owns the tables and is used by the init container migrate only; studio_app, the restricted role of the running application, is created when PostgreSQL initialises an empty volume. The owner password never reaches the running application.
  • Component oidc: sign-in through OIDC_ISSUER_URL, client secret read from the Secret.
  • Taxonomy axes: the base ships a default configuration file with three neutral axes (ConfigMap modaka-studio-config-file), which a target replaces. The Studio does not start without at least one axis.
  • Secret modaka-studio-env: provider keys; the key of the AI provider is required to start.
  • Component database-network-policy: only the Studio reaches its database. Optional because a target may not allow the NetworkPolicy kind.

No existing recipe is changed: nothing breaks for current targets.

Verified

  • bun run validate passes, base alone and with each component.
  • The production build of the Studio was started with exactly the settings the recipe renders (ConfigMap and configuration file, components oidc and database-network-policy): the sign-in page answers 200. A first version of the recipe lacked the AI model and the axes and did not start; fixed in the second commit.
  • The init script was run in a local postgres:17-alpine: studio_app is created without superuser nor BYPASSRLS, with a password holding quotes.
  • The Studio migrations were applied to that database as the owner; the restricted role then reads the account tables and can neither delete an account nor create a table.

Not verified

  • The recipe was not deployed to a cluster.
  • The base names the image tag develop. Local accounts are not in a released image yet (modaka/studio pull request 13): a target must pin a release that includes them.
  • The image registry asks for credentials today: a target adds its own imagePullSecrets.

🤖 Generated with Claude Code

Closes #13 ## What New recipe `modaka-studio`: Modaka Studio with its own PostgreSQL, behind Traefik with a cert-manager certificate. - **Two database roles.** `studio_owner` owns the tables and is used by the init container `migrate` only; `studio_app`, the restricted role of the running application, is created when PostgreSQL initialises an empty volume. The owner password never reaches the running application. - **Component `oidc`**: sign-in through `OIDC_ISSUER_URL`, client secret read from the Secret. - **Taxonomy axes**: the base ships a default configuration file with three neutral axes (ConfigMap `modaka-studio-config-file`), which a target replaces. The Studio does not start without at least one axis. - **Secret `modaka-studio-env`**: provider keys; the key of the AI provider is required to start. - **Component `database-network-policy`**: only the Studio reaches its database. Optional because a target may not allow the NetworkPolicy kind. No existing recipe is changed: nothing breaks for current targets. ## Verified - `bun run validate` passes, base alone and with each component. - The production build of the Studio was started with exactly the settings the recipe renders (ConfigMap and configuration file, components `oidc` and `database-network-policy`): the sign-in page answers 200. A first version of the recipe lacked the AI model and the axes and did not start; fixed in the second commit. - The init script was run in a local `postgres:17-alpine`: `studio_app` is created without superuser nor `BYPASSRLS`, with a password holding quotes. - The Studio migrations were applied to that database as the owner; the restricted role then reads the account tables and can neither delete an account nor create a table. ## Not verified - The recipe was not deployed to a cluster. - The base names the image tag `develop`. Local accounts are not in a released image yet (modaka/studio pull request 13): a target must pin a release that includes them. - The image registry asks for credentials today: a target adds its own `imagePullSecrets`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(modaka-studio): recipe with its PostgreSQL and optional OpenID Connect sign-in (#13)
All checks were successful
CI / CI (pull_request) Successful in 28s
f0dc66203d
Deploys Modaka Studio with a dedicated PostgreSQL holding accounts, sessions and the
tenant registry. Migrations run in an init container as the owner role, so that the
owner password never reaches the running application, which connects with a restricted
role created when the database is initialised.

Optional components: oidc (sign-in through OIDC_ISSUER_URL), config-file (instance
configuration from a ConfigMap of the target) and database-network-policy.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
fix(modaka-studio): ship the settings the Studio needs to start (#13)
All checks were successful
CI / CI (pull_request) Successful in 33s
e7a033f39f
The Studio refuses to start without an AI model, the key of its AI provider and at
least one taxonomy axis. The base now sets the model, requires the Secret
modaka-studio-env and ships a default configuration file with three neutral axes,
which replaces the optional component config-file.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
crapougnax merged commit eb3229485e into develop 2026-11-16 20:11:03 +00:00
crapougnax deleted branch feat/13-modaka-studio-recipe 2026-11-16 20:11:03 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/catalog!14
No description provided.