App workflow Moodle + WordPress + Docker workloads

Deploy a learning platform beside WordPress

Assess Moodle requirements and validate course access and operational ownership. 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 team already has a public WordPress site but needs learner enrolment, assignments and completion records. It evaluates Moodle as a separate learning platform.

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

Define the boundary with WordPress

Where
Training owner and site map
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Public course description, learner entry point, identity owner
Action
Keep the WordPress page as public program information and Moodle as the learner system. Map where a visitor moves from enquiry to enrolment and who approves an account.
Expected result
A documented handoff between two services.
Verify
Follow one sample visitor link to the intended enrolment entry point.
If it fails
If the requirement is only public reading, avoid a separate LMS.

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

Step 2 of 5

Choose domain and identity model

Where
DNS plan, WordPress links and Moodle authentication
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Moodle hostname, WordPress link, login provider
Action
Plan a distinct Moodle HTTPS host and separate login path. If shared sign-in is required, scope a real integration and fallback; do not infer SSO from shared hosting.
Expected result
An identity decision visible to users.
Verify
Check link target and describe where learners receive credentials.
If it fails
If identity ownership is unresolved, keep enrolment closed.

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

Step 3 of 5

Deploy a separate Moodle service

Where
xCloud One-Click Apps dashboard
Permissions
Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
Inputs
Compatible server, template, hostname, admin owner
Action
Install Moodle on its own site. Record separate site ID, administrator and backups; leave WordPress deployment untouched.
Expected result
A reachable Moodle login independent of WordPress.
Verify
Open both public URLs and compare certificates and redirects.
If it fails
If WordPress redirects or cookies interfere, correct routing before linking publicly.

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

Step 4 of 5

Test the public-to-learner handoff

Where
WordPress page, Moodle enrolment screen and test inbox
Permissions
Authorized Moodle application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Sample link, invited learner, email route
Action
Publish or preview a WordPress course link, follow it as a signed-out visitor, then complete a test Moodle enrolment or invitation with an authorized admin.
Expected result
A visitor reaches the right course entry with expected identity flow.
Verify
Confirm invitation and login work without WordPress administrator rights.
If it fails
If enrolment fails, fix Moodle/mail configuration; do not add false SSO language to the page.

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

Step 5 of 5

Assign separate operating owners

Where
WordPress Site Backup and Moodle 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
Two site IDs, data scopes, support contacts
Action
Document which team updates WordPress content versus Moodle learner data, and inspect backups and recovery targets for both.
Expected result
A two-service runbook with no hidden shared-state assumption.
Verify
Have each owner find their service and last Completed backup.
If it fails
If Moodle database or moodledata is missing from coverage, delay real learner enrolment.

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