Book a demo
Book a demo
Login

App workflow BookStack + WordPress + Docker workloads

Deploy a knowledge base beside WordPress

Assess BookStack or Wiki.js requirements and validate authentication and content workflows. Check the named site's prerequisites, task result, backup scope and recovery handoff with xCloud.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

A WordPress support site needs an internal knowledge base with editors and read-only staff. The team compares BookStack and Wiki.js rather than forcing articles into the marketing CMS.

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 knowledge structure

Where
Content inventory and app upstream docs
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Article types, editors, readers, attachments
Action
Sample the existing support content and decide whether BookStack structure or Wiki.js pages match how people browse and revise it.
Expected result
A selected app with a migration sample.
Verify
Ask an editor to locate a sample article in the proposed structure.
If it fails
If the structure hides common tasks, adjust the choice before deployment.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · BookStack security and app key · BookStack page editing, revisions and permissions

Step 2 of 5

Check template and data path

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
Chosen template, Docker server, hostname
Action
Confirm template availability, persistent database/files and server compatibility. Identify app-specific secrets such as BookStack APP_KEY.
Expected result
A deployable plan and data inventory.
Verify
Review actual template fields and free storage.
If it fails
If a secret or data path is unknown, do not claim a complete restore path.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · BookStack security and app key

Step 3 of 5

Deploy the knowledge 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
Create the app site through the supported dashboard path and record its first-run URL. Leave administrator and reader/editor configuration to the selected application.
Expected result
A reachable BookStack or Wiki.js 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

Publish a sample article

Where
BookStack or Wiki.js editor
Permissions
Authorized Knowledge application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Non-sensitive article, attachment and revision
Action
Complete first administrator setup, restrict public registration and assign limited editor and reader roles. Create one article with an attachment, change a paragraph, test search and revision recovery, then link it from WordPress after URL stability.
Expected result
A usable content workflow.
Verify
Confirm a reader sees the current page but cannot edit it or see a private book. In fresh reader and editor sessions, inspect the allowed menus.
If it fails
If permissions expose private books or permit a reader to edit, correct roles before migration. If search or attachments fail, troubleshoot storage and indexing before importing bulk content.

Sources: BookStack security and app key · BookStack page editing, revisions and permissions · Wiki.js page creation and editing · Wiki.js user groups and permissions

Step 5 of 5

Plan backup and handover

Where
xCloud Docker Backup and app export
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, uploads, app key/config, owner
Action
Record all app-specific data needed to restore the article and attachment. Check a Completed backup and a safe recovery test plan.
Expected result
A recoverable knowledge base and editorial owner.
Verify
Reopen the sample article after test restart and inspect backup scope.
If it fails
If an export omits attachments or keys, include them through another documented backup route.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · BookStack security and app key

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