Metadata Settings

Per-repo identity, governance, deployment, and build metadata stored in the database.

API

GET /api/v1/repos/{owner}/{repo}/metadata -- read settings (public, no auth required)
PUT /api/v1/repos/{owner}/{repo}/metadata -- update (merge semantics, only provided fields change)

Key Changes (v1.27.0)

Endpoint renamed from /manifest to /metadata
package_type renamed to extension_type
display_name is now read-only -- computed as {ExtensionType} - {Name} (e.g. Package - MokoSuiteBackup)
.mokogitea/manifest.xml file is no longer used -- metadata is API-only
GET endpoint is public (no authentication required)
Deploy fields added: deploy_host, deploy_port, deploy_user, deploy_path, docker_image, docker_registry, container_name, health_url

Web UI

Settings are available in repo Settings > Metadata tab. The web form supports: name, org, description, license, platform, extension type, entry point, and deploy fields.

Deploy Fields

Used by CI/CD workflows for automated deployment:

Field	Description
`deploy_host`	SSH hostname for deployment
`deploy_port`	SSH port
`deploy_user`	SSH username
`deploy_path`	Deployment directory on host
`docker_image`	Docker image name
`docker_registry`	Docker registry URL
`container_name`	Docker container name
`health_url`	URL to check after deployment

Pages