Facade
The wippy/facade module provides a portable iframe facade that loads and configures the Wippy frontend from a CDN. It serves an HTML shell that creates an iframe pointing to the frontend bundle, handles authentication, and bridges configuration between the backend and frontend.
Add the module to your project:
wippy add wippy/facadewippy installDeclare the dependency:
version: "1.0"namespace: app
entries: - name: gateway kind: http.service addr: :8090 lifecycle: auto_start: true
- name: api kind: http.router meta: server: app:gateway prefix: /api/public
- name: dep.facade kind: ns.dependency component: wippy/facade version: "*" parameters: - name: server value: app:gateway - name: router value: app:apiConfiguration Parameters
Seção intitulada “Configuration Parameters”| Parameter | Required | Default | Description |
|---|---|---|---|
server | yes | — | HTTP server for static and iframe serving |
router | yes | — | Public API router for config endpoint |
fe_facade_url | no | https://web-host.wippy.ai/webcomponents-1.0.21 | Base URL for iframe frontend bundle |
fe_entry_path | no | /iframe.html | Iframe HTML entry point path |
App Identity
Seção intitulada “App Identity”| Parameter | Default | Description |
|---|---|---|
app_title | Wippy | Title shown in sidebar |
app_name | Wippy AI | Full application name |
app_icon | wippy:logo | Iconify icon reference |
Feature Flags
Seção intitulada “Feature Flags”| Parameter | Default | Description |
|---|---|---|
hide_nav_bar | false | Hide the left navigation sidebar |
disable_right_panel | false | Disable the right sidebar panel |
start_nav_open | false | Navigation drawer open by default |
show_admin | true | Show admin panel toggle |
allow_select_model | false | Allow user to select LLM model |
session_type | non-persistent | Chat session persistence: non-persistent or persistent |
history_mode | hash | Browser history mode: hash or history |
hide_session_selector | false | Oculta a UI de selecao de sessao |
Tematizacao
Seção intitulada “Tematizacao”Tres escopos se aplicam: global (em todos os lugares), host (o chrome ao redor do iframe) e children (conteudo dentro do iframe).
| Parametro | Escopo | Padrao | Descricao |
|---|---|---|---|
custom_css | global | Import do Google Fonts | CSS injetado em todos os niveis |
css_variables | global | {} | Mapa JSON de CSS custom properties |
icon_sets | global | [] | URLs de conjuntos de icones Iconify |
host_custom_css | host | "" | CSS apenas para o chrome do host |
host_css_variables | host | {} | CSS custom properties apenas para o host |
host_icon_sets | host | [] | Conjuntos de icones apenas para o host |
children_custom_css | children | "" | CSS apenas para o conteudo do iframe |
children_css_variables | children | {} | CSS custom properties apenas para o conteudo do iframe |
login_path | — | /login.html | Caminho de redirecionamento para usuarios nao autenticados |
JSON opcional hostConfig
Seção intitulada “JSON opcional hostConfig”Cada um dos parametros abaixo e uma string codificada em JSON; os padroes sao vazios ({} ou []). Eles sao repassados inalterados ao frontend sob hostConfig.
| Parametro | Padrao | Descricao |
|---|---|---|
api_routes | {} | Sobrescritas de rotas para o frontend |
additional_nav_items | [] | Entradas extras na sidebar |
state_cache | {} | Configuracao do cache de estado do frontend |
allow_additional_tags | [] | Tags HTML adicionais permitidas no chat |
chat | {} | Sobrescritas de UI do chat |
axios_defaults | {} | Padroes do cliente HTTP axios do frontend |
Config Endpoint
Seção intitulada “Config Endpoint”The facade registers GET /facade/config on the configured router. The frontend fetches this on load:
{ "facade_url": "https://web-host.wippy.ai/webcomponents-...", "iframe_origin": "https://web-host.wippy.ai", "iframe_url": "https://web-host.wippy.ai/webcomponents-.../iframe.html?waitForCustomConfig", "login_path": "/login.html", "env": { "APP_API_URL": "https://api.example.com", "APP_AUTH_API_URL": "https://api.example.com", "APP_WEBSOCKET_URL": "wss://api.example.com" }, "routePrefix": "https://api.example.com", "axiosDefaults": { "...": "..." }, "theming": { "global": { "customCSS": "...", "cssVariables": {}, "iconSets": {} }, "host": { "customCSS": "...", "cssVariables": {}, "iconSets": {}, "i18n": { "app": { "title": "Wippy", "icon": "wippy:logo", "appName": "Wippy AI" } } }, "children": { "customCSS": "...", "cssVariables": {} } }, "hostConfig": { "session": { "type": "non-persistent" }, "history": "hash", "showAdmin": true, "allowSelectModel": false, "startNavOpen": false, "hideNavBar": false, "disableRightPanel": false, "hideSessionSelector": false, "apiRoutes": { "...": "..." }, "additionalNavItems": [], "stateCache": { "...": "..." }, "allowAdditionalTags": [], "chat": { "...": "..." } }}A URL da API e lida da variavel de ambiente PUBLIC_API_URL; APP_WEBSOCKET_URL e derivada substituindo http:// por ws:// ou https:// por wss://. A tematizacao tem tres escopos (global, host, children) — host.i18n carrega a marca da aplicacao. As chaves de hostConfig estao em camelCase e sao montadas a partir dos parametros do facade: session_type, history_mode, show_admin, allow_select_model, start_nav_open, hide_nav_bar, disable_right_panel, hide_session_selector, mais opcionalmente api_routes, additional_nav_items, state_cache, allow_additional_tags, chat e axios_defaults.
Navigation Sidebar
Seção intitulada “Navigation Sidebar”Pages registered via wippy/views appear in the sidebar automatically based on their metadata:
entries: - name: dashboard kind: registry.entry meta: type: view.page name: dashboard title: Dashboard icon: tabler:chart-bar group: Analytics group_icon: tabler:chart-dots group_order: 10 order: 1 announced: true secure: true url: https://cdn.example.com/dashboard/Sidebar Groups
Seção intitulada “Sidebar Groups”Pages with the same group value are collected into collapsible sections. Groups are sorted by group_order (lower first), pages within groups by order.
| Field | Description |
|---|---|
group | Category name displayed in sidebar |
group_icon | Icon for the category header |
group_order | Sort position of the group (lower = higher) |
group_placement | "sidebar" (in sidebar) or "default" (main area only) |
Pages without a group appear as top-level items.
Controlling Visibility
Seção intitulada “Controlling Visibility”| Field | Effect |
|---|---|
announced: true | Page appears in sidebar navigation |
announced: false | Page hidden from navigation but still accessible via URL |
inline: true | Internal page, hidden from all UI listings |
hide_nav_bar: true | Facade parameter — hides the entire left sidebar |
Publishing with Embedded Assets
Seção intitulada “Publishing with Embedded Assets”When publishing a component that includes static files (like the facade’s public/ directory), use --embed to include fs.directory entries in the package:
wippy publish --embed facade:public_filesWithout --embed, fs.directory entries are excluded from the published package. The --embed flag accepts entry IDs or names matching fs.directory entries.
See Also
Seção intitulada “See Also”- Views - Page and component system
- HTTP Server - HTTP service configuration
- Framework Overview - Framework module usage