Skip to content
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.

Chart migration to use media-common #37

Closed
4 tasks
dirtycajunrice opened this issue Sep 6, 2020 · 5 comments
Closed
4 tasks

Chart migration to use media-common #37

dirtycajunrice opened this issue Sep 6, 2020 · 5 comments

Comments

@dirtycajunrice
Copy link
Contributor

dirtycajunrice commented Sep 6, 2020

Candidate charts that would work as an umbrella templated media-common chart

  • bazarr
  • nzbget
  • sabnzbd
  • dashmachine

(are there more? will add to the list as needed)

@carpenike
Copy link
Member

Could add dashmachine if organizrr is apart of it.

@bjw-s
Copy link
Contributor

bjw-s commented Sep 7, 2020

I'll take a crack at migrating nzbget

@bjw-s
Copy link
Contributor

bjw-s commented Sep 9, 2020

It doesn't like we'll be able to do a 1:1 migration of nzbget because of the integrated OpenVPN container :( That may be be resolved by some sort of additionalContainers directive in media-common, but is that a direction we're willing to go? It will make media-common a super flexible chart template, but maybe that defeats its' purpose.

@dirtycajunrice
Copy link
Contributor Author

@bjw-s so check this out. The point was to be able to swiss-army-knife other stuff into it. My proposal:
Make a openvpn library chart that is added as a dependency when requested and we can add an additionalContainers section like you said where this will utilize that and inject it in.

@cubic3d
Copy link
Contributor

cubic3d commented Sep 28, 2020

nzbhydra2 also fits the pattern

@onedr0p onedr0p closed this as completed Nov 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants