feat(settings): repo settings tab for manifest.xml / update stream metadata #315

New Issue

2026-05-31T14:15:03Z

jmiller commented

2026-05-31 14:15:03 +00:00

Summary

Add a new "Update Feed" tab in repo settings that exposes manifest.xml fields for configuring how the repository appears in update feeds (Joomla updates.xml, Dolibarr JSON).

Motivation

Currently, update feed metadata (display names, descriptions, platform type, version format) is either hardcoded or derived from repo metadata. Repos need a dedicated settings UI to configure:

Display name — how the extension appears in update feeds (e.g. "Moko CRM Module" vs the repo name)
Update description — short text shown to end-users in their CMS update manager
Platform type — joomla / dolibarr / both (already partially exists as RepoUpdatePlatform)
Version format — how tags map to version strings in the feed
Minimum platform version — e.g. "Joomla 4.0" or "Dolibarr 16.0"
Extension type — component, module, plugin, package (Joomla) or module (Dolibarr)
Folder/element — Joomla-specific manifest identifiers
Info URL — link shown in the update manager for more details
Icon URL — extension icon in update feeds

Schema Reference

Fields align with the moko-platform manifest schema at:

And the existing structure in repos.

Implementation Plan

Model: Add table (or extend existing ) with the above fields
Router: handler in
Template: with form fields
Navbar: Add tab to
Integration: Update and to read these settings when generating feeds

UI Mockup

Settings > Update Feed tab with sections:

Identity: Display name, description, icon URL, info URL
Platform: Type selector (Joomla/Dolibarr/Both), minimum version, extension type
Joomla-specific (shown when platform includes Joomla): element, folder, client (site/admin)
Versioning: Version format pattern, channel mapping rules

## Summary Add a new **"Update Feed"** tab in repo settings that exposes manifest.xml fields for configuring how the repository appears in update feeds (Joomla updates.xml, Dolibarr JSON). ## Motivation Currently, update feed metadata (display names, descriptions, platform type, version format) is either hardcoded or derived from repo metadata. Repos need a dedicated settings UI to configure: - **Display name** — how the extension appears in update feeds (e.g. "Moko CRM Module" vs the repo name) - **Update description** — short text shown to end-users in their CMS update manager - **Platform type** — joomla / dolibarr / both (already partially exists as RepoUpdatePlatform) - **Version format** — how tags map to version strings in the feed - **Minimum platform version** — e.g. "Joomla 4.0" or "Dolibarr 16.0" - **Extension type** — component, module, plugin, package (Joomla) or module (Dolibarr) - **Folder/element** — Joomla-specific manifest identifiers - **Info URL** — link shown in the update manager for more details - **Icon URL** — extension icon in update feeds ## Schema Reference Fields align with the moko-platform manifest schema at: And the existing structure in repos. ## Implementation Plan 1. **Model**: Add table (or extend existing ) with the above fields 2. **Router**: handler in 3. **Template**: with form fields 4. **Navbar**: Add tab to 5. **Integration**: Update and to read these settings when generating feeds ## UI Mockup Settings > Update Feed tab with sections: - **Identity**: Display name, description, icon URL, info URL - **Platform**: Type selector (Joomla/Dolibarr/Both), minimum version, extension type - **Joomla-specific** (shown when platform includes Joomla): element, folder, client (site/admin) - **Versioning**: Version format pattern, channel mapping rules ## Related - #239 (update server feature — this adds the settings UI for it) - #304 (permissions — uses TypeLicenses unit, this would need similar access control) --- *— Claude Opus 4.6 (1M context) <noreply@anthropic.com>*

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#315