User:Mjb/Logitech Media Server
It's early 2017 and I'm playing with my new SqueezeBox Boom. It's a great mini boom box which gets all its music over a LAN or WiFi connection. It can play Internet radio (Pandora, SHOUTcast, etc.) as well as audio from your own music library via Logitech Media Server or a DLNA server.
I ran into an issue with Logitech Media Server on my system, though, because my library has hundreds of Windows shortcut files. Some of these point to folders elsewhere in the same tree. Logitech Media Server currently doesn't really detect these loops, so it endlessly scans the same set of folders.
On the support forum, in late December 2016, I suggested detecting when a folder has already been visited, or just offering a configuration option to prevent the following of links to folders entirely. The main developer said he couldn't get to it until after New Year's. I suspect he has already forgotten about it and won't be getting around to it at all. So I'm going to see if I can build the software myself, make the changes I want, test them, and maybe submit a pull request on GitHub.
There are no instructions, though, so I have to figure out how to do it myself.
Preparation
1. Get one or both:
- GitHub Desktop (a GUI for basic repo management)
- Git for Windows (Git BASH, Git GUI, shell integration)
2. Fork both of these repositories:
Forking is a GitHub (not Git) feature; it means you will make a writable copy of the repos in your GitHub account, to use as a starting point. You have to do this from the GitHub website; go to each of the URLs above and click on Fork. Don't worry; you'll still be able to track changes made to the upstream repos!
If you don't fork, and just clone directly from the repos, you will not be able to push your changes to the server (unless you have been given access by the repo owners) and you will not be able to even make pull requests. So don't do that.
3. Clone (make a local copy of) the forks on your local machine, where you will be making your own development. You can do the cloning in GitHub Desktop or Git GUI, or from the command line (e.g. in Git BASH).
...to be continued...
