Runique Admin — Tera Variables per View

These variables are injected into every route by the framework's Request extractor, before any admin handler runs.

static_runique Fields

{{ static_runique.static_url }}   {# Base URL for assets, e.g. /static #}
{{ static_runique.static_dir }}   {# Physical directory on disk #}

Route: GET /admin/login

inject_context is not called — variables resource, resources, and resource_key are not available.

Required keys — login

csrf_token, site_title, lang

error is optional — present only after a POST failure. On POST failure, base section i18n keys are also injected.

Minimal example:

{% extends "admin/admin_template.html" %}

{% block title %}{{ admin_login_title }}{% endblock %}

{% block content %}
<div class="login-container">
    <h1>{{ admin_login_title }}</h1>
    <p>{{ admin_login_subtitle }}</p>

    {% if error %}
    <div class="alert alert-danger">{{ error }}</div>
    {% endif %}

    <form method="POST" action="{{ admin_prefix }}/login">
        <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
        <div>
            <label>{{ admin_login_label_username }}</label>
            <input type="text" name="username" required>
        </div>
        <div>
            <label>{{ admin_login_label_password }}</label>
            <input type="password" name="password" required>
        </div>
        <button type="submit">{{ admin_login_btn_submit }}</button>
    </form>
</div>
{% endblock %}

The login template extends admin_template.html (empty blocks contract), not admin_base.html — sidebar and topbar must not appear on the login page.

Route: GET /admin/

inject_context is not called. current_resource is explicitly None.

Required keys — dashboard

resources, resource_counts, current_page

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ admin_dashboard_title }}{% endblock %}

{% block content %}
<h1>{{ admin_dashboard_title }}</h1>
<p>{{ admin_dashboard_subtitle }}</p>

{% if resources %}
<h2>{{ admin_dashboard_card_resources }}</h2>
<table class="table">
    <thead>
        <tr>
            <th>{{ admin_dashboard_th_resource }}</th>
            <th>{{ admin_dashboard_th_key }}</th>
            <th>{{ admin_dashboard_th_permissions }}</th>
            <th>{{ admin_dashboard_th_actions }}</th>
        </tr>
    </thead>
    <tbody>
        {% for res in resources %}
        <tr>
            <td>{{ res.title }}</td>
            <td><code>{{ res.key }}</code></td>
            <td>{{ res.permissions.list | join(sep=", ") }}</td>
            <td>
                <a href="{{ admin_prefix }}/{{ res.key }}/list">
                    {{ admin_dashboard_btn_list }}
                    {% if resource_counts[res.key] %}({{ resource_counts[res.key] }}){% endif %}
                </a>
                <a href="{{ admin_prefix }}/{{ res.key }}/create">{{ admin_dashboard_btn_create }}</a>
            </td>
        </tr>
        {% endfor %}
    </tbody>
</table>
{% else %}
<p>{{ admin_dashboard_empty_title }}</p>
<p>{{ admin_dashboard_empty_desc }}</p>
{% endif %}
{% endblock %}

Route: GET /admin/{resource}/list

Pagination

Columns

Sorting

Search

Filter sidebar

Note: active_filters is pre-populated for all list_filter columns (value "" if inactive). Tera raises an error on missing keys — this pre-init prevents it. Multiple columns can have a non-empty value simultaneously: filter links preserve active filters from other columns.

Required keys for template override

Referenced via runique::utils::constante::admin_ctx::list::REQUIRED:

entries, total, page, page_count, has_prev, has_next,
prev_page, next_page, visible_columns,
sort_by, sort_dir, sort_dir_toggle, search

The i18n variables for the list section are listed in the global variables above.

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ resource.title }}{% endblock %}

{% block content %}
<div class="d-flex justify-content-between align-items-center mb-3">
    <h1>{{ resource.title }}
        <small class="text-muted fs-6">{{ total }} {{ admin_list_entries_count }}</small>
    </h1>
    <a href="{{ admin_prefix }}/{{ resource_key }}/create" class="btn btn-primary">
        {{ admin_list_btn_create }}
    </a>
</div>

{% if entries %}
<table class="table">
    <thead>
        <tr>
            <th>{{ admin_list_th_id }}</th>
            {# add columns based on the model #}
            <th>{{ admin_list_th_actions }}</th>
        </tr>
    </thead>
    <tbody>
        {% for entry in entries %}
        <tr>
            <td>{{ entry.id }}</td>
            <td>
                <a href="{{ admin_prefix }}/{{ resource_key }}/{{ entry.id }}/detail">{{ admin_list_btn_detail }}</a>
                <a href="{{ admin_prefix }}/{{ resource_key }}/{{ entry.id }}/edit">{{ admin_list_btn_edit }}</a>
                <a href="{{ admin_prefix }}/{{ resource_key }}/{{ entry.id }}/delete">{{ admin_list_btn_delete }}</a>
            </td>
        </tr>
        {% endfor %}
    </tbody>
</table>
{% else %}
<p>{{ admin_list_empty_title }}</p>
<p>{{ admin_list_empty_desc }}</p>
<a href="{{ admin_prefix }}/{{ resource_key }}/create">{{ admin_list_btn_create_first }}</a>
{% endif %}
{% endblock %}

Route: GET /admin/{resource}/create

Each entry in m2m_fields exposes:

Tera example:

{% if m2m_fields is defined and m2m_fields %}
  {% for field in m2m_fields %}
  <div class="form-group">
    <label>{{ field.label }}</label>
    {% for choice in field.choices %}
    <label>
      <input type="checkbox"
             name="m2m_{{ field.field_name }}__{{ choice[0] }}"
             value="1">
      {{ choice[1] }}
    </label>
    {% endfor %}
  </div>
  {% endfor %}
{% endif %}

Required keys — create

form_fields, is_edit

The i18n variables for the create section are listed in the global variables above.

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ admin_create_title }} — {{ resource.title }}{% endblock %}

{% block content %}
<h1>{{ admin_create_title }} — {{ resource.title }}</h1>
<p class="text-muted">{{ admin_create_card_info }}</p>

<form method="POST" action="{{ admin_prefix }}/{{ resource_key }}/create">
    {# csrf.js handles the token automatically for admin forms #}
    {% if form_fields.html %}
        {{ form_fields.html | safe }}
    {% else %}
        <p>{{ admin_create_no_fields }}</p>
    {% endif %}
    <button type="submit" class="btn btn-primary">{{ admin_create_btn_submit }}</button>
    <a href="{{ admin_prefix }}/{{ resource_key }}/list" class="btn btn-secondary">{{ admin_create_btn_cancel }}</a>
</form>
{% endblock %}

Route: GET /admin/{resource}/{id}/edit

Tera example (with pre-selection):

{% if m2m_fields is defined and m2m_fields %}
  {% for field in m2m_fields %}
  <div class="form-group">
    <label>{{ field.label }}</label>
    {% for choice in field.choices %}
    <label>
      <input type="checkbox"
             name="m2m_{{ field.field_name }}__{{ choice[0] }}"
             value="1"
             {% if choice[0] in field.selected %}checked{% endif %}>
      {{ choice[1] }}
    </label>
    {% endfor %}
  </div>
  {% endfor %}
{% endif %}

Required keys — edit

form_fields, is_edit, object_id

The i18n variables for the edit section are listed in the global variables above.

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ admin_edit_title }} — {{ resource.title }} #{{ object_id }}{% endblock %}

{% block content %}
<h1>{{ admin_edit_title }} — {{ resource.title }} <small>#{{ object_id }}</small></h1>
<p class="text-muted">{{ admin_edit_card_info }}</p>

<form method="POST" action="{{ admin_prefix }}/{{ resource_key }}/{{ object_id }}/edit">
    {% if form_fields.html %}
        {{ form_fields.html | safe }}
    {% else %}
        <p>{{ admin_edit_no_fields }}</p>
    {% endif %}
    <button type="submit" class="btn btn-primary">{{ admin_edit_btn_submit }}</button>
    <a href="{{ admin_prefix }}/{{ resource_key }}/list" class="btn btn-secondary">{{ admin_edit_btn_cancel }}</a>
</form>
{% endblock %}

Route: GET /admin/{resource}/{id}/detail

Required keys — detail

object_id

entry is optional — absent if get_fn is not configured on the resource. The i18n variables for the detail section are listed in the global variables above.

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ admin_detail_title }} — {{ resource.title }} #{{ object_id }}{% endblock %}

{% block content %}
<h1>{{ admin_detail_title }} — {{ resource.title }} <small>#{{ object_id }}</small></h1>

{% if entry %}
<dl class="row">
    {% for key, value in entry %}
    <dt class="col-sm-3">{{ key }}</dt>
    <dd class="col-sm-9">{{ value }}</dd>
    {% endfor %}
</dl>
{% endif %}

<a href="{{ admin_prefix }}/{{ resource_key }}/list" class="btn btn-secondary">{{ admin_detail_btn_list }}</a>
<a href="{{ admin_prefix }}/{{ resource_key }}/{{ object_id }}/edit" class="btn btn-primary">{{ admin_detail_btn_edit }}</a>
<a href="{{ admin_prefix }}/{{ resource_key }}/{{ object_id }}/delete" class="btn btn-danger">{{ admin_detail_btn_delete }}</a>
{% endblock %}

Route: GET /admin/{resource}/{id}/delete

Required keys — delete

object_id

entry is optional — absent if get_fn is not configured on the resource. The i18n variables for the delete section are listed in the global variables above.

Minimal example:

{% extends "admin/admin_base" %}

{% block title %}{{ admin_delete_title }} — {{ resource.title }} #{{ object_id }}{% endblock %}

{% block content %}
<h1>{{ admin_delete_heading }}</h1>

<div class="alert alert-danger">
    <strong>{{ admin_delete_warning_title }}</strong>
    <p>{{ admin_delete_warning_desc }}</p>
    {% if entry %}
    <p>{{ admin_delete_warning_of }} <strong>#{{ object_id }}</strong></p>
    {% endif %}
    <p>{{ admin_delete_warning_irreversible }}</p>
</div>

<form method="POST" action="{{ admin_prefix }}/{{ resource_key }}/{{ object_id }}/delete">
    <button type="submit" class="btn btn-danger">{{ admin_delete_btn_confirm }}</button>
    <a href="{{ admin_prefix }}/{{ resource_key }}/list" class="btn btn-secondary">{{ admin_delete_btn_cancel }}</a>
</form>
{% endblock %}

{{ admin_create_title }}

Do not use | default(value="...") — i18n variables are always present when a language is configured.

Using .templates() in the builder replaces the template for all resources:

RuniqueApp::builder(config)
    .with_admin(|a| a
        .templates(|t| t
            .with_list("my_theme/list")
            .with_create("my_theme/create")
            .with_edit("my_theme/edit")
            .with_detail("my_theme/detail")
            .with_delete("my_theme/delete")
            .with_dashboard("my_theme/dashboard")
            .with_login("my_theme/login")
            .with_base("my_theme/admin_base")
        )
    )
    .build().await?

Overridden templates have access to the same variables as the default templates.