A name, a tagline, a logo, a favicon and the launcher icons derived from it; the Middle-earth strings as data; themes as token sets; and a stylesheet for what none of that reaches. All four are on one page, in one settings group. The snapshot is a Jinja global over a process-level cache, because render() has no session and four render paths never reach it at all -- the sign-in page, the error pages, the offline page and the SSE fragments. A context value would have had to be threaded through every one and would still have missed those. It being a global is also what lets mark() branch on an uploaded logo without any of its six call sites learning about branding; the macro that renders the sidebar link is called brandlink now, because a macro imported as `brand` shadows the global for the whole template and took out every page at once. Defaults in code and overrides in the database, as the prompt fragments do, with one difference stated in the module: an empty fragment means off, an empty flavour string means the shipped wording. And blanked rather than dropped -- settings_store.update merges, so an omitted key leaves what was stored last time and "I typed the default back in" would store something different from "I changed nothing". A custom theme sets a handful of tokens and inherits the rest, and the inheritance is a CSS fact: tokens.css matches [data-base="shire"] as well as [data-theme="shire"], so a custom light theme lands on parchment rather than four light colours on near-black. Values are validated on read rather than on save, because a theme written straight into the settings table still has to produce a stylesheet that parses -- a `}` in a value ends the rule and silently breaks every rule after it. The soft variants are derived from the accent, or a changed accent leaves focus rings in the old hue and reads as half-working. /branding.css is a route, not an inline block: an external stylesheet has no HTML context to escape from. The link carries a content hash, so a save is not left to the browser's cache, and it is deliberately outside the service worker's precache list, which is versioned by the release. The instance name moved off /admin/general rather than being duplicated there. An upgrade keeps it: the general row is read as a seed exactly while the branding row has never mentioned the name, which is `key in row` and not `row[key] is truthy` -- the two read alike would resurrect the old name underneath a cleared one. The theme list stops being a hard-coded pair in five places. Every failure mode in that area is silent, so it is driven under a DOM stub as well as tested. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
133 lines
5.3 KiB
HTML
133 lines
5.3 KiB
HTML
{% extends "admin/_layout.html" %}
|
|
{% from "_macros.html" import icon %}
|
|
{% set section = "images" %}
|
|
|
|
{% block title %}{{ workflow.name or "New workflow" }} - {{ brand.name }}{% endblock %}
|
|
{% block heading %}{{ workflow.name or "New workflow" }}{% endblock %}
|
|
|
|
{% block admin_content %}
|
|
<nav class="crumbs">
|
|
<a class="crumbs__back" href="/admin/images">
|
|
{{ icon("chevron-right", "icon--sm crumbs__icon") }} Image generation
|
|
</a>
|
|
</nav>
|
|
|
|
{% if error %}
|
|
<div class="alert alert--error">{{ icon("warning", "icon--sm") }} <span>{{ error }}</span></div>
|
|
{% endif %}
|
|
|
|
<form method="post"
|
|
action="{{ '/admin/images/workflows' if is_new else '/admin/images/workflows/' ~ workflow.id }}"
|
|
class="form-grid">
|
|
<section class="card">
|
|
<h2 class="card__title">What it is</h2>
|
|
|
|
<div class="field">
|
|
<label class="field__label" for="name">Name</label>
|
|
<input class="input" id="name" name="name" required maxlength="120"
|
|
value="{{ workflow.name }}" placeholder="SDXL, photographic">
|
|
<p class="field__hint">Shown to you, in the list.</p>
|
|
</div>
|
|
|
|
<div class="field">
|
|
<label class="field__label" for="slug">Name the model uses</label>
|
|
<input class="input input--mono" id="slug" name="slug" required maxlength="48"
|
|
value="{{ workflow.slug }}" placeholder="sdxl-photo">
|
|
<p class="field__hint">
|
|
Lowercase letters, digits, hyphens and underscores. This is what the model
|
|
writes when it picks this workflow.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="field">
|
|
<label class="field__label" for="description">Description</label>
|
|
<textarea class="textarea" id="description" name="description" rows="3"
|
|
placeholder="Photographic and slow. Best for people, interiors and product shots at 1024px.">{{ workflow.description }}</textarea>
|
|
<p class="field__hint">
|
|
The only thing the model has to choose with, so say what this is
|
|
<em>for</em> rather than what it contains. It never sees the graph.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="field">
|
|
<label class="checkbox">
|
|
<input type="checkbox" name="enabled" value="true" {{ 'checked' if workflow.enabled }}>
|
|
<span>Offer this workflow</span>
|
|
</label>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="card">
|
|
<h2 class="card__title">The workflow</h2>
|
|
<div class="field">
|
|
<label class="field__label" for="workflow">ComfyUI API format</label>
|
|
<textarea class="textarea input--mono" id="workflow" name="workflow" rows="20"
|
|
spellcheck="false">{{ workflow_text }}</textarea>
|
|
<p class="field__hint">
|
|
Export this from ComfyUI with <strong>Export (API)</strong>, not Save — the
|
|
two formats are different and only the API one can be submitted.
|
|
</p>
|
|
<p class="field__hint">
|
|
Then put a placeholder where each value goes. A placeholder that is the
|
|
<em>whole</em> value keeps its type, so
|
|
<code>"steps": {{ '{{steps}}' }}</code> sends the number 20 rather than the
|
|
text “20”; one inside a longer string is substituted as text, so
|
|
<code>"{{ '{{prompt}}' }}, masterpiece"</code> works. Anything you leave out
|
|
takes its default.
|
|
</p>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="card">
|
|
<h2 class="card__title">The placeholders</h2>
|
|
<p class="card__lede">
|
|
Every hole a template may carry, what it fills, and what it resolves to
|
|
right now. <code>{{ '{{prompt}}' }}</code> is required — without it every
|
|
image would be the same one, whatever anybody typed.
|
|
</p>
|
|
{# The current value beside each name, the way /admin/prompts shows a
|
|
variable's. A legend that lists names and not values answers "what may I
|
|
write" and not "what will happen", and the second is the question
|
|
somebody has while looking at a workflow that came out wrong. #}
|
|
<div class="ref-list">
|
|
{% for name, kind, what, current in placeholder_help %}
|
|
<div class="ref-row">
|
|
<code>{{ '{{' ~ name ~ '}}' }}</code>
|
|
<span>
|
|
{{ what }}
|
|
{% if name == "prompt" %}<strong>Required.</strong>{% endif %}
|
|
</span>
|
|
<code class="faint">{{ current }}</code>
|
|
</div>
|
|
{% endfor %}
|
|
</div>
|
|
<p class="field__hint">
|
|
Two of these are not spelled the way ComfyUI spells them, which is the
|
|
mistake that costs an afternoon: <code>{{ '{{model}}' }}</code> fills
|
|
<code>ckpt_name</code> and <code>{{ '{{sampler}}' }}</code> fills
|
|
<code>sampler_name</code>.
|
|
</p>
|
|
<p class="field__hint">
|
|
The right-hand column is what an omitted placeholder resolves to today —
|
|
the instance defaults from the image settings page, falling back to the
|
|
built-in floor. A model may override any of them except
|
|
<code>{{ '{{batch}}' }}</code>, which is yours alone.
|
|
</p>
|
|
</section>
|
|
|
|
<div class="btn-row">
|
|
<button class="btn btn--primary" type="submit">
|
|
{{ "Add workflow" if is_new else "Save changes" }}
|
|
</button>
|
|
<a class="btn btn--ghost" href="/admin/images">Back</a>
|
|
{% if not is_new %}
|
|
<button class="btn btn--danger" type="submit" formnovalidate
|
|
formaction="/admin/images/workflows/{{ workflow.id }}/delete"
|
|
data-confirm-button="Delete the workflow “{{ workflow.name }}”? Chats that used it fall back to the default.">
|
|
Delete
|
|
</button>
|
|
{% endif %}
|
|
</div>
|
|
</form>
|
|
{% endblock %}
|