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>
34 lines
1.4 KiB
HTML
34 lines
1.4 KiB
HTML
{% extends "base.html" %}
|
|
{% block title %}Jobs — roledesk{% endblock %}
|
|
|
|
{% block content %}
|
|
<h1>Jobs</h1>
|
|
|
|
<p class="lede"><strong>pull</strong> runs the whole chain: every board, then extract, embed and score. <strong>extract</strong>, <strong>embed</strong> and <strong>score</strong> run one stage on their own. The buttons come from <code>/api/jobs/kinds</code>, so a new <code>@job</code> under <code>app/jobs/</code> appears here without an edit.</p>
|
|
|
|
<section class="card">
|
|
<h2>Start something</h2>
|
|
<div id="kinds" class="buttons">
|
|
<span class="muted">loading the job kinds…</span>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="card">
|
|
{# The queue's own element, served by its own router. Two lines, and the
|
|
module owns what they draw — see pipeline/web/static/jobs.js.
|
|
|
|
The heading is the app's, because the element takes up no space while
|
|
nothing is running — that is its `idle="hide"` default, and a strip that
|
|
is always there is furniture — and a card with nothing in it and nothing
|
|
above it reads as something that failed to load. #}
|
|
<h2>What is running</h2>
|
|
<p class="muted small" id="idle">Nothing at the moment. Press one of the buttons above.</p>
|
|
<script type="module" src="/_jobs/jobs.js"></script>
|
|
<desk-jobs></desk-jobs>
|
|
</section>
|
|
{% endblock %}
|
|
|
|
{% block scripts %}
|
|
<script src="{{ asset('jobs.js') }}"></script>
|
|
{% endblock %}
|