# Werkregie-Dashboard in mode `server` on a host — e.g. ~/.config/werkregie/dashboard.yml there.
port: 31234                   # the localhost port of the booked "eigener Serverdienst"
windowHours: 168

# Claude Code and Codex come from the relays, not from the host
claude: { enabled: false }
codex: { enabled: false }

server:
  bindAddress: 127.0.0.1      # Apache proxies to it via .htaccess
  publicBaseUrl: https://regie.example.org/
  # stateDir: ~/.local/state/werkregie   # access-token and relays.json
  relayStaleSeconds: 30
  relayGoneSeconds: 120

werkators:
  - name: javagil
    url: https://werkator.example.org
    controlTokenEnv: WERKREGIE_WERKATOR_JAVAGIL   # private repositories; or controlToken: <token>

giteas:
  - name: javagil
    url: https://git.example.org
    tokenEnv: WERKREGIE_TOKEN_JAVAGIL             # or token: <token>; no tea on the host
    pullRequests: all

# task boards with what is assigned to you (modes local and server); only type taiga so far
# taskboards:
#   - name: team
#     type: taiga
#     url: https://taiga.example.org        # the web pages; the API is found in their conf.json
#     # apiUrl: https://taiga-api.example.org/api/v1   # only where conf.json does not tell it
#     usernameEnv: WERKREGIE_TAIGA_USER     # or username: <name>
#     passwordEnv: WERKREGIE_TAIGA_PASSWORD # never the password itself
#     projects: [shop, docs]                # project slugs, as in the address of a project
#     statuses: [In Arbeit, Bereit]         # most important first; other open statuses follow