App workflow Moodle + Docker workloads

Deploy Moodle for a course program

Confirm template availability and upstream sizing, mail, storage, and backup requirements. Check the named site's prerequisites, task result, backup scope and recovery handoff with xCloud.

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

A training provider is launching a Moodle course program with assignments and completion records. It needs a full site data plan before enrolling paying learners.

Choose the approach

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

Set course program boundaries

Where
Training plan and Moodle admin
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Course count, users, grading, retention
Action
Choose one pilot course with a sample assignment, enrolment route and completion criterion. Decide who administers learner records.
Expected result
A clear course acceptance test.
Verify
Confirm teacher and learner expectations in writing.
If it fails
If no one owns enrolment and grading, postpone real signups.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Moodle course copy and backup scope

Step 2 of 5

Check Moodle prerequisites

Where
xCloud template, Moodle docs, server
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Database, moodledata, cron, mail, server capacity
Action
Confirm current Moodle template and persistent data paths. Check background job/cron and email provider requirements before deployment.
Expected result
A compatible hosting plan.
Verify
Inspect server headroom and template settings.
If it fails
If cron cannot run, do not promise timely notifications or completion tasks.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Moodle course copy and backup scope · xCloud WordPress site email configuration

Step 3 of 5

Deploy the Moodle host

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 Moodle through the supported dashboard path and record its first-run URL. Leave course and role setup to the Moodle administrator.
Expected result
A reachable Moodle 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

Step 4 of 5

Exercise course lifecycle

Where
Moodle course and gradebook
Permissions
Authorized Moodle application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Lesson, assignment, learner submission
Action
Complete Moodle administrator setup, configure a pilot course and assign teacher and learner roles. Enrol a test learner, complete a lesson, submit an assignment and review it as teacher.
Expected result
A traceable learner-to-teacher result.
Verify
Match submission time and grade/completion record. Sign in separately as teacher and learner and confirm the learner cannot edit course settings.
If it fails
If learner rights exceed the approved role, correct them before enrolment. If jobs stall, inspect Moodle cron and mail before adding users.

Sources: Moodle course copy and backup scope · Moodle teacher role · Moodle enrolment · Moodle assignment activity · Moodle cron CLI

Step 5 of 5

Rehearse data recovery

Where
Moodle backup tools 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, moodledata, config, course backup
Action
Create a course backup for portability and verify a Completed whole-app backup separately. Restore a pilot copy where safe and inspect learner progress.
Expected result
A recovery plan covering site and course state.
Verify
Compare sample submission and file after restore.
If it fails
If only the course backup exists, do not call the full Moodle service recoverable.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Moodle course copy and backup scope

Maintenance

Recovery decisions

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 Moodle 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

Sources

Continue

Explore all use cases