Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss: Architecture for different *arr #112

Open
BlackDark opened this issue Nov 20, 2024 · 0 comments
Open

Discuss: Architecture for different *arr #112

BlackDark opened this issue Nov 20, 2024 · 0 comments
Labels
question Further information is requested

Comments

@BlackDark
Copy link
Contributor

Two solutions which could be tackled:

  • merge everything as one product (as it currently is)

    • has maybe some drawbacks that we have to always check or write some factory pattern to be always in the correct *arr tooling if we have some specialties. Because not everything can be generalized.
  • Write some skeleton/template for common things and split into own products for each stack

    • like configarr-sonarr, configarr-radarr, configarr-readarr, ...
    • code specifics stick only where it needs to be
    • can still result in lot of duplicate code and increased maintenance.

This issue is just to keep track of the idea nothing which needs to be implemented right now.

@BlackDark BlackDark added the question Further information is requested label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant