Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the Gitea application. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
For a Docker app, identify persistent volumes, bind mounts, external databases and app-level export requirements. A Docker backup briefly stops the app, and an in-place restore replaces current state. Agree a maintenance window and owner before any action that interrupts the service or overwrites data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Illustrative situation
A development team runs Gitea for private repositories. It needs to review access and prove that both Git objects and database metadata can be restored together.
Choose the approach
A green Gitea page does not prove pushes, hooks or repository permissions work.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Gitea backup guidance recommends a stopped instance for a consistent native dump of database and repositories.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Review repo access
- Where
- Gitea organizations and repositories
- Permissions
- Authorized Gitea application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Team membership, private repos, branch rules
- Action
- List owners, write users and viewers for a representative repo. Check departed members and branch protection.
- Expected result
- A current access map.
- Verify
- Test viewer cannot push and developer can push permitted branch.
- If it fails
- If permissions are broader than policy, correct them before adding repos.
Sources: Gitea backup and restore · Gitea repository and organization permissions
Step 2 of 5
Exercise Git path
- Where
- Developer client and Gitea web view
- Permissions
- Authorized Gitea application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Test repo, SSH/HTTPS credential, sample commit
- Action
- Clone and push one harmless commit, then fetch it from a second authorized account. Compare commit hash and webhook results if used.
- Expected result
- A functional repository path.
- Verify
- Check web history and local Git hash match.
- If it fails
- If web login works but push fails, inspect keys, hooks and protocol separately.
Sources: Gitea backup and restore · Gitea repository and organization permissions
Step 3 of 5
Check data growth and jobs
- Where
- xCloud Docker site and Gitea admin
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Disk, logs, indexer, migration status
- Action
- Inspect repository storage, app logs and any running migrations before maintenance. Avoid backup during active migration.
- Expected result
- A maintenance-ready status.
- Verify
- Compare disk headroom to current repo data.
- If it fails
- If migration is active, wait and recheck before snapshot.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Back up and restore Docker apps · Gitea backup and restore
Step 4 of 5
Verify consistent backup
- Where
- Gitea backup docs and xCloud 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
- DB, repository files, attachments, config, snapshot
- Action
- Plan a brief stop for native dump or rely on documented stopped-app Docker snapshot only after confirming every path is included. Check Completed state.
- Expected result
- A consistent recovery point.
- Verify
- Inspect snapshot paths and sampled repository contents.
- If it fails
- If database and Git files are captured at different times, plan a corrected backup.
Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Gitea backup and restore
Step 5 of 5
Rehearse and document
- Where
- Isolated Gitea test site
- Permissions
- Authorized Gitea application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Snapshot, test user, commit hash
- Action
- Restore the sample into isolation, regenerate hooks if installation path changed, then clone and push a test commit.
- Expected result
- A tested repository recovery.
- Verify
- Match existing commit and new push in restored web UI.
- If it fails
- If hooks fail, keep production intact and update recovery steps.
Sources: Gitea backup and restore · Gitea repository and organization permissions
Maintenance
Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Recovery decisions
Before data recovery, identify incident time, completed backup, target and records created after the snapshot. Preserve current evidence and live data before replacement.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Use the documented dashboard or application recovery procedure with the authorized owner. Repeat the task-specific limited-user check; reconcile newer records before reopening writes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Gitea backup and restore · Gitea repository and organization permissions · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
AI handoff
Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
- An authorized Gitea administrator must configure and test app users, content, integrations and business rules in the app.
- Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
- Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage
- repo-ops decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Review repo access Exercise Git path Check data growth and jobs Verify consistent backup
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Verify consistent backup Rehearse and document