Cameronsplaze / Cameronsplaze/AWS-ContainerManager
[Feature] Add a `Jellyfin` config to Examples
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 5
Description
### Is your feature request related to a problem? Please describe.
Figure out where the pain-points are for "media-server" type containers, so we can fix and support them too. You don't have to worry about storage with this ticket, that's covered by https://github.com/Cameronsplaze/AWS-ContainerManager/issues/10. Test with a few movies/shows, to make sure it's functional for now.
[Jellyfin](https://jellyfin.org/) itself is the server [I'm most interested in (with this chart)](https://github.com/Protektor-Desura/Archon/wiki/Compare-Media-Servers).
### Describe the solution you'd like
The server is open to the web, make sure it's secure:
- Connections should be encrypted:
- If there's a way, use [Jellyfin's LetEncrypt](https://jellyfin.org/docs/general/post-install/networking/advanced/letsencrypt) through the EnvVars to setup https. The problem with the [Let's Encrypt and Docker](https://jellyfin.org/docs/general/post-install/networking/advanced/letsencrypt#lets-encrypt-and-docker) method is that it requires a second container, AND manually-running commands. Hopefully one of the other options on the list works with JUST the jellyfin container.
- Hide the http traffic inside of a VPN tunnel (https://github.com/Cameronsplaze/AWS-ContainerManager/issues/160). ESPECIALLY with https://github.com/jellyfin/jellyfin/issues/5415 too.
- Some ports, disabled:
- From [External Access](https://jellyfin.org/docs/general/post-install/networking/#external-access), port 7359 for [`Automatic discovery`/`Client Discovery`](https://jellyfin.org/docs/general/post-install/networking/#port-bindings) should be blocked/disabled.
### Describe alternatives you've considered
N/A
### Acknowledgements
- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing configurations under Examples and the container/network entry point used by them. Review how environment variables, HTTPS, VPN routing, and exposed ports are configured, then validate the Jellyfin example with several movies and shows. Done means the example is functional, encrypted or tunneled as specified, and does not expose the disabled discovery port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- infrastructure, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100