app/main.py assembles it in the boilerplate's order, auth.connect first, then the queue with the scheduler and the pages. TABS is Roles, Applications, Agents, Companies, Jobs, Schedules, Messages and Account: the alpha page's three views become templates on the boilerplate's base.html, driven by static/roles.js (the old app.js) through api() and toasts.js, over the unchanged JSON routes. Companies lists every board with its open roles and the affinity control. A 422 is one sentence, so a toast never reads [object Object]. Config takes the boilerplate's shape: APP_CONFIG or config.yaml, a missing file is the defaults, an unknown key is an error. roles.yaml is gone; config.yaml is the committed default and carries the starter agents. pull is now a job that asks for the pull cascade, because a schedule enqueues a job kind; its default schedule, every 6h, is declared beside it in app/jobs/cascade.py. pull_batch's targets are keyword-only so the Jobs tab offers no batch button. `app worker` is the boilerplate's; `app job` still drains a queue of its own and fires no schedules. test_coupling holds pipeline, auth and desk apart (desk may import pipeline) and plugins to desk; test_architecture keeps app's layers, now with main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
42 lines
1.3 KiB
YAML
42 lines
1.3 KiB
YAML
# roledesk's default config, committed. config.example.yaml documents every
|
|
# key; anything left out here takes the default written there.
|
|
server:
|
|
host: 127.0.0.1
|
|
port: 8790
|
|
database: roledesk.db
|
|
timezone: Europe/Berlin
|
|
auth:
|
|
rp_name: roledesk
|
|
cookie: roledesk_session
|
|
plugin_paths:
|
|
- plugins
|
|
workers:
|
|
llm: 4
|
|
http: 8
|
|
cpu: 1
|
|
extract:
|
|
enabled: false
|
|
model: claude-haiku-4-5-20251001
|
|
embed:
|
|
model: sentence-transformers/all-MiniLM-L6-v2
|
|
sources: {}
|
|
# Starter search agents, imported once into an empty table. Edit them on the
|
|
# Agents tab afterwards; this list is not read again.
|
|
agents:
|
|
- name: Berlin backend
|
|
intent: >-
|
|
Senior backend engineer. Python and Go services, PostgreSQL, event-driven
|
|
systems, APIs and data pipelines on Kubernetes in the cloud. Wants
|
|
ownership of production systems in a product company.
|
|
gates:
|
|
- {field: place, values: [Berlin], mode: require}
|
|
- {field: remote, values: [hybrid, remote], mode: prefer, weight: 0.2}
|
|
- name: Remote EU stretch
|
|
intent: >-
|
|
Staff or lead engineer role, fully remote from Europe. Platform and
|
|
infrastructure work, distributed systems, developer tooling, technical
|
|
leadership across teams.
|
|
gates:
|
|
- {field: remote, values: [remote], mode: require}
|
|
- {field: country, values: [DE, NL, AT, CH], mode: prefer, weight: 0.2}
|