[elliotblackburn]

Description

Fusion RSS is another feed reader with support for rss, atom, and JSON feeds. It's an alternative to FreshRSS with slightly less functionality and specifically only supports a single tenant (user) which keeps it quite simple.

This adapts my own docker compose file that I use in my setup, for the ScaleTail project.

Related Issues

• None.

Verification

• docker compose config --quiet from each changed service directory, with dummy values for required variables
• The stack started, Tailscale is healthy, and the service is reachable through the Tailnet
• The main function of the service works, and its data survives a restart
• rumdl check --config .markdownlint.yml . on the whole repository, and git diff --check

Impact on existing users

• None.

Checklist

• I have performed a self-review of my code and followed the templates structure.
• I did not commit a working auth key, password, token, or other credential.
• The service README uses the headings of the template, in the same order, and is up to date.
• I added, removed, or renamed the service in the root README.md, in alphabetical order, or this PR does not change the list of services.

Additional Context

• None.

[jackspiering]

Thanks @elliotblackburn, this is a really clean stack. I compared it with the template and CONTRIBUTING.md, checked it against the Fusion v1.3.0 source, and started it on a test Tailnet.

Live test: both containers came up healthy and the image's health check passes. Serve answers over HTTPS. Logging in works, a wrong password gets 401, and a wrong TAILNET_NAME or a foreign Origin gets 403, exactly as the README warns. I added a feed and the articles came in, the Fever API authenticates with md5(fusion:<password>), and everything survived a full docker compose down / up. Also nice: FUSION_TRUSTED_PROXIES makes the login rate limit see the real Tailnet client IP.

One thing to change:

• PR title: please rename it to Fusion: new service. CONTRIBUTING.md uses the format <Service>: what changes, with Service replaced by the service's name.

Thanks again!

[elliotblackburn]

Hey @jackspiering, thanks for the thorough test and review. Ah my misread on the title requirement, sorry about that. I've fixed that now!