Book a demo
Book a demo
Login

Operations BookStack + Docker workloads

Operate a team knowledge base

Review access, content ownership, backup scope, update path, and search behavior. 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 team maintains a BookStack or Wiki.js knowledge base. It needs to keep article edits, readers, attachments and app-specific secrets recoverable.

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

Identify app and content scope

Where
xCloud app site and knowledge admin
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
BookStack or Wiki.js, sensitive spaces, contributors
Action
Confirm deployed app/version and list critical books or pages, attachments and reader groups.
Expected result
A specific content and access baseline.
Verify
Open a sample article as a limited reader.
If it fails
If a restricted page is visible publicly, fix access before other maintenance.

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

Review roles and shares

Where
App groups and permissions
Permissions
Authorized Knowledge application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Editors, readers, guests, page rules
Action
Compare current users with team roster. For Wiki.js check global rights and page rules; for BookStack inspect role permissions and visibility.
Expected result
A least-privilege editor/reader map.
Verify
Test allowed edit and denied edit from separate accounts.
If it fails
If a reader can change content, correct app permissions.

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 3 of 5

Test edit and revision recovery

Where
BookStack/Wiki.js page history
Permissions
Authorized Knowledge application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Harmless page, sample attachment
Action
Make a small edit, inspect history, revert it and verify attachment/search behavior remains intact.
Expected result
A demonstrated editorial recovery path.
Verify
Compare before/after text and limited-reader view.
If it fails
If history or attachments fail, investigate storage before bulk edits.

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 4 of 5

Inspect persistent backup

Where
App docs 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, uploads, config, BookStack APP_KEY
Action
Map all storage needed to reconstruct pages, users and attachments. Verify Completed Docker backup and key custody.
Expected result
A complete backup scope.
Verify
Restore a safe test copy and open sample article with attachment.
If it fails
If key/config is absent, do not claim encrypted app state is recoverable.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · BookStack security and app key · BookStack page editing, revisions and permissions

Step 5 of 5

Assign ongoing owners

Where
Knowledge runbook
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Content reviewer, app updater, backup owner
Action
Set review cadence for stale pages, access changes and app updates. Document different restore procedures for the selected app.
Expected result
A maintained knowledge service.
Verify
Have another editor locate last revision and backup.
If it fails
If no app owner remains, freeze broad edits until ownership transfers.

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

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