Add healthcheck, backup support, and update documentation #5

Merged
ammaratef45 merged 1 commits from yaup/jellyfin:pr/healthcheck-backup-improvements-v2 into main 2026-01-22 01:11:39 +00:00
Contributor

Overview

Adds healthcheck, backup support, and improved documentation to the jellyfin recipe. Updates recipe status from score 1 (alpha) to score 3 (beta).

I compared this to the YunoHost recipe for reference when implementing the changes.

Description

  • Added healthcheck using Jellyfin's /health endpoint
  • Configured backup-bot-two for backups
  • Updated README

Tested generally and validated YAML syntax with docker compose config

The backup functionality needs additional testing / confirmation - I haven't tested the backup yet. If someone can help verify the backup configuration or notices something missing, I'd appreciate it!

## Overview Adds healthcheck, backup support, and improved documentation to the jellyfin recipe. Updates recipe status from score 1 (alpha) to score 3 (beta). I compared this to the [YunoHost](https://github.com/YunoHost-Apps/jellyfin_ynh) recipe for reference when implementing the changes. ## Description - Added healthcheck using Jellyfin's `/health` endpoint - Configured backup-bot-two for backups - Updated README Tested generally and validated YAML syntax with `docker compose config` The backup functionality needs additional testing / confirmation - I haven't tested the backup yet. If someone can help verify the backup configuration or notices something missing, I'd appreciate it!
yaup added 2 commits 2026-01-20 18:48:56 +00:00
- Enable healthcheck using Jellyfin's /health endpoint
- Add compose.backup.yml for automated backups via offen/docker-volume-backup
- Support S3-compatible and SSH/SFTP backup storage
- Remove deprecated version attribute from compose files
- Expand .env.sample with backup configuration options
- Rewrite README with backup docs, hardware transcoding guide, and troubleshooting
decentral1se requested review from 3wordchant 2026-01-20 19:28:10 +00:00
decentral1se requested review from aadil 2026-01-20 19:28:10 +00:00
decentral1se requested review from ammaratef45 2026-01-20 19:28:22 +00:00
decentral1se requested review from cas 2026-01-20 19:28:22 +00:00
decentral1se reviewed 2026-01-20 19:32:18 +00:00
decentral1se left a comment
Owner

Welcome @yaup 👋 Thanks for the PR! I just one minor comment and have asked for review from others who commit to this recipe. If you don't get anything back shortly, please come ask in the matrix community channels for help.

Welcome @yaup 👋 Thanks for the PR! I just one minor comment and have asked for review from others who commit to this recipe. If you don't get anything back shortly, please come ask in the matrix community channels for help.
README.md Outdated
@ -3,3 +3,2 @@
> One line description of the recipe
> The Free Software Media System
<!-- metadata -->
Owner

This wild metadata comment system is actually what we parse with abra:

https://docs.coopcloud.tech/abra/recipes/#status-features-score

🙈

This wild metadata comment system is actually what we parse with `abra`: > https://docs.coopcloud.tech/abra/recipes/#status-features-score 🙈
Author
Contributor

Hi!

Ah, makes sense! Thanks for the doc reference.

Hi! Ah, makes sense! Thanks for the doc reference.
ammaratef45 marked this conversation as resolved
ammaratef45 requested changes 2026-01-20 22:59:55 +00:00
ammaratef45 left a comment
Owner

Hmm, I need some convincing regarding backups. coop-cloud apps use backup-bot-two for backups which allows enabling and configuring backups using labels and env values.

Is there a benefit from breaking consistency on how we do backups?

Hmm, I need some convincing regarding backups. coop-cloud apps use [backup-bot-two](https://git.coopcloud.tech/coop-cloud/backup-bot-two) for backups which allows enabling and configuring backups using labels and env values. Is there a benefit from breaking consistency on how we do backups?
yaup force-pushed pr/healthcheck-backup-improvements-v2 from 9abbd967c6 to 30bbd37d48 2026-01-21 03:47:04 +00:00 Compare
Author
Contributor

Hmm, I need some convincing regarding backups. coop-cloud apps use backup-bot-two for backups which allows enabling and configuring backups using labels and env values.

Is there a benefit from breaking consistency on how we do backups?

Ah, missed this in my speed run of the docs. No benefit that I know of, let's go with backup bot.

> Hmm, I need some convincing regarding backups. coop-cloud apps use [backup-bot-two](https://git.coopcloud.tech/coop-cloud/backup-bot-two) for backups which allows enabling and configuring backups using labels and env values. > > Is there a benefit from breaking consistency on how we do backups? Ah, missed this in my speed run of the docs. No benefit that I know of, let's go with backup bot.
yaup force-pushed pr/healthcheck-backup-improvements-v2 from 30bbd37d48 to 2b4e18cea2 2026-01-21 04:18:19 +00:00 Compare
ammaratef45 approved these changes 2026-01-21 04:58:07 +00:00
ammaratef45 left a comment
Owner

looks legit!

looks legit!
compose.yml Outdated
@ -41,2 +38,4 @@
proxy:
external: true
# coop-cloud recipe metadata
Owner

Hmmm, do these comments do anything?

Hmmm, do these comments do anything?
Author
Contributor

Oops, good catch. Some leftover notes I didn't mean to commit. Removed them.

Oops, good catch. Some leftover notes I didn't mean to commit. Removed them.
yaup force-pushed pr/healthcheck-backup-improvements-v2 from 2b4e18cea2 to cde0595c77 2026-01-21 18:53:50 +00:00 Compare
Owner

Alright, jellyfin is still without a maintainer so I'll just allow myself and merge your change

Alright, jellyfin is still without a maintainer so I'll just allow myself and merge your change
ammaratef45 merged commit ef7397f0ba into main 2026-01-22 01:11:39 +00:00
Sign in to join this conversation.
No description provided.