I use Jellyfin. I think in your use case, each user would be setup have their own library. You can enable or disable library on a per user basis as will as a per client basis.
Downside is that the default web interface isn’t great as a music player. It does the job but it’s not great.
Other hand, multiple music-first clients exist for a lot of different platforms. Odds are good you can find a client that suits how you listen to music.
Edit: said collection when I meant library.
It’s doable. Stick to the 7b models and it should work for the most part, but don’t expect anything remotely approaching what might be called reasonable performance. It’s going to be slow. But it can work.
To get a somewhat usable experience you kinda need an Nvidia graphics card or an AI accelerator.
@tal has already given a really good answer. To add to it, this thread might help you some: https://lemmy.sdf.org/comment/11963996 I was asked what I thought was “better” than a raspberry pi. Came back with an eBay search and a trio of suggestions in the price range of a Pi 4. TLDR is whatever you have currently will probably work fine but if you need to buy hardware, there are plenty of low cost options. And of course, Pi’s also work fine for anything they are capable of, which is most things.
When I started self hosting, Raspberry Pi’s were the cheapest option available. I learned fairly quickly that the SD card was the weakest part of them but not long after the Pi3 came out we were able to boot off of USB drives which solved that issue. I think I had 8 SSDs hanging off of one pi before I finally decided to plop down the money for a tower. I then added a pair of 6 port SATA cards and added even more storage to that system. Eventually I was hosting so many things that I was running out of RAM, So I bought a second used tower, this one with a much newer processor and a lot more RAM. Now I run both with the old system running as a NAS and the new system hosting my other services. I wouldn’t stress about hardware too much. Hardware can grow with you, to a point.
Mini PCs are too small to house internal drives
Most mini PCs I’ve heard of (and quite a few thin clients) use m.2 drives for internal storage. Not difficult to upgrade. I’ve also heard of a few that had ports and internal space for 2.5 inch SSDs.
I don’t know of ANY reason to go with spinning-platters, nowadays.
Price per terabyte is lower on HDDs. For bulk storage they are currently the best path. SSDs are catching up though, and there are cases where a SSD based NAS does make sense. But most folks at home don’t have the network capability to fully utilize their speed. Network becomes the bottleneck.
Given how old the system is, I’m not sure how long it would survive that type of duty. Power up and downs are a lot rougher on components than if they just stay running.
If you switch the HDD for a pair of SDD (one storage, one swap), it would be somewhat useable. Better to increase the amount of RAM if possible. If I remember correctly, 2-4 GB of RAM was not uncommon at this time period. Although NixOS or a really light Debian install might be able to stay within that amount of RAM. So yea, I think it’s feasible.
Good Idea? Perhaps not so much. That proc has a TDP of 95W. Haven’t found anything on it’s idle power draw, but I’d guess that that system would have a fairly heavy power draw. The slow speed of the processor and low amount of RAM would probably limit the amount of traffic you could put through it. Additionally, the age of the components would probably cause reliability issues.
Generally I like to tell folks to use what they have. Repurposing old hardware is better for the environment and usually the wallet, but this system would probably would not be my first, second or even third choice for any workload. I haven’t found a benchmark comparing the two, but I think a Pi3 would probably run dead even with this system at a far lower power draw. Although the Pi3’s ethernet does run on it’s USB bus (I think), along with it’s storage, so that would slow it down for this workload. If you wanted to run traffic faster, I would probably look into the used micro PC market at the $75-$150 USD price point. This system is old enough to vote. Something merely 10 years old would be considerably faster.
It’s not difficult to self host. Pretty light on resources. Documentation on how to do so could use some work though. I believe I used a docker image to get up and running.
The main reason I personally don’t allow public signups on my instance is that US law is rather chaotic. If section 230 gets cancelled or repealed I don’t want to be held responsible for what some random person chose to write. It may not be a big risk at the moment but I don’t have the mental bandwidth to deal with it.
Heads up on the copyright thing. Copyright is different nation to nation. @ThePowerOfGeek@lemmy.world seems to be out of the UK or EU. Not sure what the copyright situation is like there but here in the US, anything you write is already protected under US copyright laws from the moment it’s published (such as when I hit “post” here), subject to any applicable agreements you’ve entered into, of course.
You don’t HAVE to register your work for it to be under copyright protection, but to doing so would give you a stronger case if you ever decided to go to court over copyright. To register a work in the US you would do so through the Copyright Office.
In general though, @ThePowerOfGeek@lemmy.world is right though, you should assume anything you put out in the wild will be used in a manner you never intended, and that you may not like.
For examples of how helpful copyright protection is in a practical sense, might want to check out c/piracy.
For something like this, I think I would use Hugo to generate a static site. You write the post using markdown then tell Hugo to regenerate the site.
If you want to publish and receive comments or feedback via the fediverse, you might take a look at WriteFreely. Simpler to use but more complicated to setup.
Wordpress is also an option, but I personally don’t like it much. I spend all my time playing with all the knobs and never actually publish anything.
https://github.com/awesome-selfhosted/awesome-selfhosted#blogging-platforms
As everyone else has said, if your time is limited, your best path is docker. You don’t need to learn all of docker, but understanding how docker compose works at a fairly high level will drastically speed up setup as well as administrative tasks like updating and backups
As for what to run, you mentioned wireguard and a notes app. The notes app could be solved without needing a central server with Obsidian and I’m not seeing the use case here for Wireguard.
I would start with what problem or pain point are you trying to solve for.
In my case, I had a bunch of IOT devices all making excessive DNS queries and I wanted a network level ad blocker so I setup PiHole (2 in fact, they run my network’s DNS).
I had a large music collection and burning mix CDs was no longer practical so I setup Jellyfin (Navidrome might have also worked), and use FinAmp on my phone.
Google started being a pain in my backside so I setup Nextcloud.
Someone got me some smart devices so HomeAssistant was setup.
I needed a way to find these services so I setup Heimdel as a dashboard.
I wanted some of these publicly available so I setup Caddy as a reverse proxy.
I’m going to have to take a look at this! Thanks!
Didn’t know they existed. Thanks!
I may not understand your question, but I use Jellyfin as the backend for my music collection. It draws metadata from MusicBrainz and passes my listen stats to ListenBrainz. I believe that those plugins are in Jellyfin’s default repository.
Right now I’m bouncing between OSs, but on Windows my CD ripper (EAC) draws metadata from MusicBrainz as well. On Linux I’ve been using K3B as a ripper which still works (nearly 20 years after I first discovered it!), but oddly for KDE software, is not as configurable as I would like. I believe it also draws metadata from MusicBrainz.
I’m just guessing myself, but I suspect it’s probably ok-ish. NextCloud is probably better security wise than most things I self host.
Follow security best practices and things should be fine.
Here’s the documentation páge I remember
Might look into running NextCloud on NixOS. Haven’t tried it myself yet but noticed NextCloud referenced in NixOS’s documentation pretty heavily. If I remember correctly it was as simple as
service.nextcloud.enable = true;
in the configuration.nix file to get it started.
Linux unplugged had an episode on it recently and said they were surprised how performative it was. Sounded like they were going to be moving their instance over to it.
Not sure if it meets your needs but I’ve been using Audiobookshelf for pulling podcasts. The default web interface is simple and straightforward and you can create secondary rss feeds if you have another podcast app you prefer. Has apps for iOS and android, though the iOS app is TestFlight. As a podcast player it’s decent. Not sure if it does notifications, I tend to disable them.
I started using it because one of the podcasts I listened to ended and I wasn’t able to go back and relisten to the episodes. Decided to start archiving the podcasts I was interested in.
Never felt that way to me, but each cat their own rat.
As frequently as I hear about Navidrome though, I may have to check it out.
For me the advantage of Docker is that a random update to my system is unlikely to crash my self hosted services. It simplifies setting up the services as well but the biggest advantage is that it is generally more stable.
Me too! Not much to look at but it’s a great player on iOS. On Linux, I like SonixD.