Declarative configuration

Keep workspace settings in version control instead of clicking through the dashboard. Quackback reads an optional config file on startup and whenever it changes, reconciles its values into your workspace, and locks those fields from in-app edits.

Note: The config file is entirely optional. Without it, every setting stays editable in the dashboard as normal. It's most useful when you manage Quackback alongside other infrastructure as code.

How it works

Quackback watches /etc/quackback/config.yaml. When the file is present:

• Every value it declares is reconciled into the workspace settings.
• Those fields become read-only in the dashboard — the UI shows them with a "Managed" badge and rejects writes.
• Any field the file doesn't declare stays freely editable.

Edit the file and Quackback re-reconciles automatically. Remove a field and that setting becomes editable again.

Warning: Secrets are never read from this file. OAuth client secrets and the SSO client secret stay encrypted in the database — set them through the dashboard.

File format

The file is a Kubernetes-style manifest:

apiVersion: quackback.io/v1
kind: QuackbackConfig
metadata:
  source: ops-repo            # optional, free-form label
spec:
  workspace:
    name: Acme Feedback
    slug: acme
    useCase: saas             # saas | consumer | marketplace | internal
  state: active               # active | suspended | deleting
  auth:
    openSignup: false
    oauth:
      password: true
      google: true
      github: false
    ssoOidc:
      enabled: true
      discoveryUrl: https://your-org.okta.com/.well-known/openid-configuration
      clientId: 0oa1example
      autoCreateUsers: true
  features:
    helpCenter: true
  tierLimits:
    maxBoards: 10
    maxPosts: null            # null means unlimited
    features:
      webhooks: true
      customCss: false

apiVersion, kind, and spec are required. Everything inside spec is optional — declare only what you want to manage.

Schema reference

spec.workspace

spec.state

spec.auth

Note: Per-domain Require SSO enforcement isn't declared in the file — manage it on the SSO page.

spec.features

A map of feature-flag names to booleans. Each key locks one flag while leaving the others UI-toggleable.

spec.tierLimits

Numeric limits — null means unlimited. Partial objects are allowed; the file only needs the limits it wants to lock.

Mount the file

With Docker, mount your config into the container:

services:
  quackback:
    volumes:
      - ./quackback-config.yaml:/etc/quackback/config.yaml:ro

For a manual install, place the file at /etc/quackback/config.yaml and make sure the Quackback process can read it.

Next steps

• Deploy with Docker — Docker Compose setup
• Environment variables — runtime configuration
• Set up single sign-on — the SSO connection this file can manage