• 1 Post
  • 5 Comments
Joined 1Y ago
cake
Cake day: Jun 19, 2023

help-circle
rss

Consider using a USB3 SSD as your boot drive if you want long term usage from your pi. The SD card is prone to failure relatively quickly on Raspian and is even worse on OSes that aren’t optimized for the PI directly.


I have a kind of complicated system for organizing my music files – some of which is admittedly way too much maintenance but it might be of interest to some.

For my general “commercial” music collection, the folder structure is roughly
Music/%Release Artist | Band%/%Album%[%Year%]/%Track No.% - %Title%.%Format%

This is simple to maintain. I basically just use MusicBrainz Picard and set up appropriate paths.

For my soundtrack collection, it gets a bit more complicated. For Anime/Film/Whatever, I have it sorted basically the same way but in a different root folder. So something like:
Music/Anime/%Release Artist | Band%/%Album%[%Year%]/%Track No.% - %Title%.%Format%

Which is also easy to maintain since most of these also have commercial releases.

But games are sorted more strangely. To put it simply, I have a folder structure that puts the console or platform first, followed by the game name and then the loose files. Since some of these files are emulated formats (.vgm, .nsf, .spc), I generally don’t bother renaming them and keep them as is and trust that the music program in question has tagging support. It also means that having them sorted by console is mostly beneficial to quickly find emulated file formats, but YMMV and I have regretted the choice on occasion.

Obviously game soundtracks are spotty when it comes to releases. Some companies have reliable metadata you can get from MusicBrainz Picard, like SquareEnix, but others have no tagging at all or very incorrect tag values. Because of this, I generally use something like VGMDB, which is usually higher quality but not always. I do have to resort to manually correcting files on occasion.

If anyone has a nice automated way to sort this stuff out, it would be a real benefit to me as well.


As an update, I think this was a side effect of how Wordpress / Gitlab was set up, where it was expecting it to be IP:PORT, which would force a redirect to the port specifically. Using the subdomain as the setting for web url seemed to resolve my problem. Thanks for the replies from everyone as all of the advice here is still really useful!


NGinx Proxy Manager and Domain Routing to Docker Services on Specific Ports
So, while this is not exactly a typical "self-hosting" question as many users might not be using domains, I would be curious if anyone else has any experience with this. I have NGinx Proxy Manager installed on a vps and a few docker instances that host various services (wordpress, a gitlab, etc etc) that I have bound to specific ports (wordpress to port 80, gitlab to port 3000, to give made up arbitrary examples.) I also have a domain and a few subdomains registered as Type A resource records that look like: [www.]somedomain[.com] [gitlab.]somedomain[.com] The essence of the question: When I go to NGinx Proxy Manager and register a "Proxy Host" for the gitlab subdomain, like: Domain: gitlab.somedomain.com Scheme: http Forward Hostname: \<IP ADDRESS HERE\> Forward Port: 3000 (AKA the port gitlab is hosted on) This works, but it comes with the drawback that the port number is then exposed in the url bar like so: `gitlab.somedomain.com:3000` So is there some way to fix this on the NGINX proxy manager side of things? Or is this a case where I'm doing this completely wrong and someone with web-dev experience can help me see the light. While it's not a huge hindrance to my use-case, it would still be nice to understand how this is supposed to work so that I can host more services myself that require domain names without having to shell out for isolated IPs. So if I hosted a lemmy or kbin, for example, I could actually configure it to use my subdomains correctly.
fedilink

You would think, of all the communities that would be comfortable with migration, it would be the folks from /r/selfhosted!

Fellow user from there, btw, nice to see we’ve got a decent pool of people on this board instead.


There is a docker internal DNS, you can just resolve IPs by service name/container_name.

Yes, and you can also control that as well by messing with docker network groups. I find the ability to network into docker servers from the host to be super simple.

What I haven’t figured out yet is whether or not I can give my docker services their own IP on my router for access from another system on a fixed or reserved IP.