Book a demo
Book a demo
Login

App workflow Jellyfin + Docker workloads

Deploy Jellyfin for a personal media library

Confirm current template and storage/transcoding requirements against upstream documentation. 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 household wants to access its own media library from Jellyfin. The owner needs a controlled user account, a small trial library and clarity about media versus app metadata backups.

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

Check media and storage rights

Where
Media owner and xCloud server
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Authorized files, storage path, expected library size
Action
Confirm the files may be hosted and the server has disk and bandwidth headroom. Identify whether media lives on a mounted external path.
Expected result
A legal, feasible library plan.
Verify
Check file ownership and a sample playable format.
If it fails
If storage is external, document its separate backup and mount recovery.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Jellyfin backup and restore

Step 2 of 5

Deploy Jellyfin

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 Docker server, app hostname, template
Action
Create the Jellyfin site with a stable HTTPS URL and record the app and server IDs. Keep public access restricted during setup.
Expected result
A reachable Jellyfin setup wizard.
Verify
Inspect HTTPS and current template version.
If it fails
If install stalls, inspect logs and storage permissions instead of recreating the site.

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

Step 3 of 5

Configure library and users

Where
Jellyfin dashboard
Permissions
Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Sample folder, metadata language, limited viewer
Action
Complete setup wizard, add a small authorized library, and create a non-admin user with access only to that library.
Expected result
A visible library for the intended viewer.
Verify
Sign in as limited user and check no other libraries appear.
If it fails
If an unwanted library is visible, correct user permissions before invitation.

Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types

Step 4 of 5

Test playback and indexing

Where
Viewer browser or client; Jellyfin logs
Permissions
Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Known media item and client device
Action
Run a library scan and play a representative item. Inspect transcoding behavior, subtitles and playback errors from the actual client.
Expected result
A successful media journey and known resource cost.
Verify
Compare playback result with CPU/RAM during the test.
If it fails
If playback stalls, isolate codec/transcode and network causes before increasing resources.

Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types

Step 5 of 5

Separate app and media backup

Where
Jellyfin Backups 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
Metadata snapshot, media path, restore owner
Action
Check Jellyfin's built-in backup options for database/metadata and xCloud coverage for app data. Protect original media separately and rehearse recovery of a small test library.
Expected result
A complete recovery map.
Verify
Verify backup files and media source remain accessible after restart.
If it fails
If media files are absent from backup, do not describe the instance as fully recoverable.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Jellyfin backup and restore · Jellyfin library administration

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