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>
14 lines
457 B
HTML
14 lines
457 B
HTML
{% extends "base.html" %}
|
|
{% block title %}{{ status }} — roledesk{% endblock %}
|
|
|
|
{% block content %}
|
|
<h1>{{ status }}</h1>
|
|
|
|
{# The server's own sentence, the same one `/api` callers get as `detail`.
|
|
Two wordings for one failure is how a page ends up telling you something
|
|
the API does not. #}
|
|
<p class="lede">{{ detail }}</p>
|
|
|
|
<p><a href="/">Back to the roles</a>, or <a href="/messages">see what the server has been saying</a>.</p>
|
|
{% endblock %}
|