Files
jobboard/app/templates/schedules.html
T
WolfandClaude Opus 5.5 59a301c351 Wire the app like the boilerplate: door, queue, schedules, eight tabs
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>
2026-09-23 12:48:12 +02:00

16 lines
927 B
HTML

{% extends "base.html" %}
{% block title %}Schedules — roledesk{% endblock %}
{% block content %}
<h1>Schedules</h1>
<p class="lede">A schedule enqueues a job kind on a cadence: <code>every 15m</code>, <code>every 6h</code>, <code>every 2d</code>, <code>daily at 06:00</code> or <code>weekly mon 07:00</code>, the clock ones read in <code>timezone</code> from <code>config.yaml</code>. The default, <code>pull</code> every 6h, is declared next to the <code>pull</code> job in <code>app/jobs/cascade.py</code>. It is a starting point: a cadence edited here, or a schedule switched off, survives restarts and deploys.</p>
<section class="card">
{# The element and its script are the scheduler's own, served by its own
router — see pipeline/web/static/schedules.js. Two lines, as with jobs. #}
<script type="module" src="/_jobs/schedules.js"></script>
<desk-schedules></desk-schedules>
</section>
{% endblock %}