Transitioning Users From NZBGet to NZBGet-ng

[tdworz]

Thanks for continuing work on NZBGet!

I'd like to start a discussion about efforts that can be made to help transition users to this fork. I personally rely on a packaged copy of NZBGet and I'd like my Linux distribution to continue to package NZBGet as it is developed in this repo. I think it would also be good to try to save people the hour I just spent researching what is going on with NZBGet as they realize the project is abandoned archived.

First, has any effort been made to reach out to @hugbug about including some sort of notice in the About section or README.md file of the nzbget/nzbget repository that this project exists? Having such a note is not uncommon and may save people a lot of time researching the situation. It can also help coalesce efforts around this project.

Beyond that, perhaps even asking for control over the NZBGet organization and nzbget.net domain is worth an effort if it has not already been tried. If @hugbug would agree to giving this project the domain, perhaps it would be worth asking for the forum database as well to preserve past discussions.

Second, has any effort been made to contact downstream packagers of NZBGet to encourage them to continue their work with this code base and the future releases published here? NZBGet is distributed by several downstream repositories.

Third, perhaps some kind of post or notice summarizing the situation could be useful, specifically in hopes that it returns prominently in search engine results. A respectful and accurate account of why this fork and project exist and plans for the future would be nice to reference in places discussing the situation. I know there is a notice on top of this repo's README.md, but perhaps a page on the NZBGet-ng website would be better.

I'd be willing to help with any of these efforts.

[faethon]

There might be quite some users that are using the Docker image from linuxserver.io, which used to be the most downloaded NZBGet docker image. It may be usefull to replicate the image, based on the NZBget-ng code to easily transition end users that are relying on the docker image from linuxserver. I noticed there are already quite some forks. Might be handy to have a docker image that is linked on this repo, and maintained from NZBGet-ng as well.

[beertje44]

ATM the situation is rather confusing, that is for users of the linux-server nzbget docker image. Which is probably the way to go these days if you want to run nzbget on Linux. I do however want to say that this initiative is a really pleasant surprise for me personally. It's just that there are mutiple forks for the linux server docker setup right now, it seems people with the right skills are fixing this on their own. So for the rest of us it is a bit confusing which fork to choose and how to get nzbget-ng up&running on docker/podman. Personally I've chosen https://github.com/bradpeczka/docker-nzbget-ng and managed to get it up&running by adding libcap-devel to the build step and libcap to the final image. Not that hard. Also I pinned the version to tag v21.4-rc1, but that is not what is mentioned inside nzbget, guess this is still work in progress? Apart from this I have some modification that allow me to run beets on music files and filebot on movies, but that is just for my setup and probably of little interest to the avarage user.

[ovizii]

I'm also interested how to transition from the linuxserver.io package to this new fork.

[beertje44]

Here you go: https://hub.docker.com/repository/docker/jb044/nzbget-ng/general

Still based on alpine 3.18, 3.19 doesn't seem to like pip for installing python deps. Also I use beets and filebot in my own nzbget scripts. So I added openjdk and python beets. If you don't need that just don't use it ;) It'll only get used if you script it.