Deploy Gitea for a small development team

Where

Development team and Gitea docs

Permissions

Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.

Inputs

Users, organizations, SSH policy, hostname

Action

Decide who creates repos, who can push and whether private repos are the default. Choose an HTTPS or SSH access method.

Expected result

An access map for the first project.

Verify

Have a developer and viewer confirm expected rights.

If it fails

If public repositories are prohibited, set policy before adding real code.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Gitea backup and restore

Where

xCloud One-Click Apps catalog

Permissions

Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.

Inputs

Gitea template, server, disk, data path

Action

Confirm the template and persistent database/repository paths, then choose a compatible Docker + NGINX server and stable hostname.

Expected result

A deployable target with adequate storage.

Verify

Inspect current template requirements and free disk.

If it fails

If repository or database path lies outside protected storage, revise backup plan.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Gitea backup and restore

Where

xCloud dashboard → One-Click Apps

Permissions

Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.

Inputs

Approved xCloud site, hostname and protected first-run administrator handoff

Action

Install through the supported dashboard path and record the Gitea first-run URL, persistent storage and generated credential handoff.

Expected result

A reachable Gitea host ready for protected application setup.

Verify

Confirm the xCloud site and hostname match the approved deployment, then verify that the expected protected first-run page is reachable.

If it fails

If the hostname, certificate or first-run page is wrong, stop application setup and resolve the hosting or access issue before entering credentials.

Sources: xCloud One Click Apps catalog · xCloud agent capability boundaries

Where

Developer terminal and Gitea UI

Permissions

Authorized Gitea application administrator or delegated role with rights for this task; hosting access alone is insufficient.

Inputs

Test key/token, branch and sample commit

Action

Complete Gitea administrator setup, create a private test repository and limited users. Clone, push a harmless commit, pull as another permitted user and verify a viewer cannot push.

Expected result

Git operations match intended rights.

Verify

Compare the commit hash in the local clone and Gitea web view. Verify signed-out users cannot browse the private test repository and a viewer cannot push.

If it fails

If repository access is public unexpectedly, correct application settings before importing code. If SSH fails but web login works, inspect key and network configuration separately.

Sources: Gitea backup and restore · Gitea repository and organization permissions

Where

Gitea backup guidance and xCloud Docker Backup

Permissions

Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption.

Inputs

Database, repositories, attachments, config, maintenance window

Action

Identify all Gitea state. Schedule a short interruption for a consistent app-level dump or validate xCloud's stopped-app snapshot, then test restoration on an isolated instance.

Expected result

A recovery method covering Git and database together.

Verify

Check restored commit and user/repo metadata.

If it fails

If repository files and DB disagree, do not reopen pushes until a consistent point is restored.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Gitea backup and restore