Note linuxserver.io in getting started

[RollingStar]

Description

Fixes #4838.

(...)

To Do

• [ ] Documentation. (If you've add a new command-line flag, for example, find the appropriate page under docs/ to describe it.)
• [ ] Changelog. (Add an entry to docs/changelog.rst near the top of the document.)
• [ ] Tests. (Encouraged but not strictly required.)

[bossanova808]

Unmaintained also now seems slightly unfair to be honest, considering e.g: https://github.com/linuxserver/docker-beets/pull/106#issuecomment-1693589020

...it's perhaps slow to be maintained, but they have both a working stable 'latest' based on the last beets release (which I believe is very old at this point) - and a working 'nightly' based on, well, nightly code (which I think is the one most people use in practise).

[RollingStar]

There is no communication between our project and LSIO which seems incredibly unhealthy. https://github.com/linuxserver/docker-beets/issues/94

[OverlordQ]

Well what type of communication are you needing? All it's doing is bundling upstream into a container. The last beets release was almost two years ago.

[RollingStar]

They modified the beets config without explanation, and when asked, they have not responded. Users express confusion over the changes that were made.

[bossanova808]

It's not some massive leap though, with this sort of media tool, is it? Copy vs. move? Sure that one video guy has his ideas on it, but...I suspect a whole host of people use this container and don't mind that change, and it's trivial to change back to copy should you wish to.

The LinuxServer docs are - across the board - pretty terrible though, for sure. Usually there are actually better guides but they are kinda hidden away in other spots, usually not even linked off their dockerhub pages etc. Case in point, I suspect the vast bulk of people using this container will have found and started with this: https://www.linuxserver.io/blog/2016-10-08-managing-your-music-collection-with-beets

...which does explain that is uses move as opposed to copy.

I suspect in terms of contact, it's one of those 'make a PR and submit to the repo' to get a response kind of scenarios.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bossanova808]

I think this should be closed or at least altered.

The Linuxserver docker is used by a lot of folks and is not unmaintained - it might be slower than desired, but a lot of us have been using it successfully for a long time.

The config warning part of it might make sense still, although I don't think it's a huge issue for anyone at the level of using a docker container for this sort of thing, so just a quick note pointing out the change from default would be all that is needed IMO.