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>
12 lines
492 B
Python
12 lines
492 B
Python
"""The web face: the tabs, the JSON routes behind them, and the Jinja
|
|
environment. The queue brings its own routes and elements (`pipeline.web`),
|
|
auth the login page and `<auth-account>` (`auth`); `app.main` puts them
|
|
together. One door for all of it."""
|
|
|
|
from __future__ import annotations
|
|
|
|
from app.web.api import router as api_router
|
|
from app.web.pages import STATIC_DIR, TABS, router as pages_router, templates
|
|
|
|
__all__ = ["STATIC_DIR", "TABS", "api_router", "pages_router", "templates"]
|