Upstream *arr configuration

[ambroisie]

Quoting from the README:

One important goal of SHB is to be the smallest amount of code above what is available in nixpkgs. It should be the minimum necessary to make packages available there conform with the contracts. This way, there are less chance of breakage when nixpkgs gets updated.

However, it looks like the *arr configuration modules go against that ethos:

• the XML generator could be upstreamed to nixpkgs.
• the various configuration options could be upstreamed to each of the *arr modules.

[ambroisie]

Here's an example of a PR that could be improved by using those options directly in nixpkgs: NixOS/nixpkgs#285119.

[ibizaman]

@ambroisie oh how I wholeheartedly agree! That is my intention but I didn't find the time to do that yet. I should probably clarify that I intend this ethos to be quite elastic. First a growing phase while I'm testing and then a shrinking phase when code gets upstreamed.

I'm focusing right now on Nextcloud and everything around it. I'm pretty satisfied with the declarative LDAP and SSO setup so far. Now, I'm working on the backup part. I do have backup working actually, but I want to make it a real SHB block with a contract an all. Like for the new SSL block.

That being said, I'd be very happy to upstream this first if you would benefit from it?

[ambroisie]

I would probably make use of it if upstreamed, yes.