NaibofTabr

however, i know nothing about self hosting. My knowledge is absolutely zero […] I dont understand nothing

This is going to be a problem, unfortunately. You’ll need to define your use case first:

• How much music do you want to have access to? Hundreds, thousands, millions of files? How large is your collection?
• Do you have downloaded copies of all the music you want to listen to? Are they all in one place, well organized and tagged? If you just have downloads in the Spotify app, you won’t be able to use those files, you don’t actually own that music. You’ll need DRM-free audio files.
• Where and how do you want to be able to access them? Just from one device like your phone? Many devices? Is having access at home good enough, or do you want to be able to access your collection while you’re away from home?
• Will you be the only user?
• What kind of budget do you have to work with?

An old PC might be enough to act as a server, but there’s more involved and the answer to what you need depends on what exactly you want to do. You will not be able to build a personal version of Spotify with just an old PC, for instance.

Never use a spreadsheet to do a database job.

Might be worth a look yourself:

Anykit USB Endoscope Camera with 8 Adjustable LED Lights, Borescope with Semi-Rigid Snake Camera, IP67 Waterproof USB Inspection Camera for Phone & Tablet (33ft) https://a.co/d/aiNASM6

I think you need to do something more to keep the panel from pulling out of its channel again. You should do what others have said, remove the door, pull the panel out, clean out all the old adhesive and caulk, and replace the panel, but you should also add something to keep the panel from leaning down away from the wall again.

A simple fix would be to screw something like this bumper into the ceiling at the end of the top channel, right at the corner of the panel so that it can’t slip out. If the ceiling is just sheet rock there then use an anchor as well.

This might not be the prettiest fix, but because the door is hanging off this panel you shouldn’t trust it to hold with adhesive only, and definitely not just silicone caulk (which is not an adhesive). Moving the door will flex the adhesive and eventually work it free again.

Run a bead of silicone around the seam. It will be more than enough to hold the glass in place.

I don’t think so, the shower door is hanging from the side of that glass panel. Silicone caulk is not an adhesive, it’s just a sealant. Opening and closing the door will break it free again.

Yeah… I wouldn’t use any web based tools if I was working on my own art, or anything commissioned for a customer, or anything copyrighted.

Of course, I wouldn’t use Adobe either after the whole AI thing.

Unnaproved software installation implies an obligation to provide user support… indefinitely.

This assumes that

1. There’s a process to read.

2. The steps in the process are complete and thorough.

Those are bad assumptions.

This is specifically caused by an update for CrowdStrike’s Falcon antivirus software, which is designed for large organizations. This won’t affect personal computers unless they’ve specifically chosen to install Falcon.

Um, if it’s “parallel” (e.g. separate from the OS package manager) then it’s not centrally managed. The OS package manager is the central management.

There might be specific use cases where this makes sense, but frankly if segregating an app from the OS is a requirement then it should be fully containerized with something like Docker, or run in an independent VM.

If a flatpack is made reasonably, then it gets library updates independent of the app developer doing it.

That feels like a load-bearing “if”. I never have to worry about this with the package manager.

Oh no, no GUI nonsense. Single, simple shell command update for the whole system so that it can be properly remotely managed, please. Something equivalent to sudo apt upgrade

This is true, the only shared libraries are usually the .NET versions, but so many apps depend on specific .NET versions that frequently the modularity doesn’t matter.

Can I sudo apt upgrade my installed flatpak apps?

Metronet will be supplying an Optical Network Terminal, probably like this one:

This is basically the equivalent of a modem for cable networks. It does not provide routing functions. You’re probably stuck with the ONT they supply, but it shouldn’t matter much, definitely not for anything internal.

It looks like Metronet normally supplies Eero WiFi mesh devices for home networking - are the ones you currently have supplied by Metronet? They might just replace the modem with the ONT and leave the existing Eero gear, or they might upgrade the Eero gear to support the higher speed available on the fiber network.

In any case, if you are using ISP-supplied network devices then you don’t control the router, which means you can’t set up things like port forwarding to access your home network from outside, or configure VLANs to segregate devices on your network, or control things like DHCP.

Technically there’s no reason you have to use the Eero devices from Metronet, you should be able to plug any router into the ONT WAN port and have internet service. If you don’t want to get too deep into network config, then any modern consumer WiFi router will work (but not a modem/router AIO device). If you want to have a bit more control, look for one that supports OpenWRT.

If you’re separating your application from the core system package manager and shared libraries, there had better be a good and specific reason for it (e.g. the app needs to be containerized for stability/security/weird dependency). If an app can’t be centrally managed I don’t want it on my system, with grudging exceptions.

Chocolatey has even made this possible in Windows, and lately for my Windows environments if I can’t install an application through chocolatey then I’ll try to find an alternative that I can. Package managers are absolutely superior to independent application installs.

You’re welcome. I tried to do basically the same thing a few years back (run a WordPress site from a RPi on my home network - and also a Minecraft server) and so I tried to write up the problems I ran into - I probably forgot some, but those are the major hurdles. I learned a lot along the way.

I should also point out that if you rent hosting space (from linode or inmotion or digitalocean or many other options) then problems 1 & 4 become much easier, and 2 & 3 go away entirely (most people don’t host public websites on their home networks because of these and other issues).

Happy to help. If you’re interested in learning networking more thoroughly, I want to point you to Professor Messer especially the Network+ content. He has far more complete explanations than I could write (and it’s free!). Even if you’re not interested in getting any certs, the explanations will be helpful.

So your goal is to host a publicly accessible static website from a computer in your home. There are a few problems you need to overcome before even worrying about configuring any software. You need some more basic networking knowledge first.

0. Basic Networking Theory - you should read a brief explanation of the OSI 7-layer network model. You don’t have to try to memorize this and you won’t really understand it until you start actually doing stuff, but you should read it for some basic terminology and to understand that there are distinct steps through which communication between computers happens.

   When you start running into problems (“why can’t I access the server? I did all the tutorial steps”), figuring out which layer the problem is in will help guide you to the solution:

   • is there a bad cable? -> 1. Physical
   • do I have the right IP address? -> 3. Network
   • is the firewall port closed? -> 4. Transport

1. Privacy/Security/Safety - don’t host a publicly accessible website from your personal computer. Just don’t. To make this happen you will have to open a hole in your network security that makes your computer accessible from the public internet. Don’t do this on your daily driver computer. Don’t do this with any device that has any files on it that you care about or any access to any personal information. Don’t.

   Set up your web server/learning environment on a clean, dedicated system. This could be an old laptop or a Raspberry Pi (an older 3B model will work just fine for this) or whatever cheap computer hardware you have, as long as it can run Linux and has a physical network port (using WiFi will give you extra headaches for getting this working). If you think you might want to expand your projects in the future, you can get a used Dell server for very little money, and add more hard drives as needed. Wipe the hard drive and install Debian or Ubuntu server as a base, there’s lots of resources out there for setting up web services on either.

2. Restricted Ports - you are most likely on a residential internet connection. Most residential ISPs close ports for security reasons, especially 80. For example, here is Cox’s list of restricted ports. You will need to find your ISP’s equivalent list and understand what you can and can’t do with your connection.

   There are workarounds, primarily through port forwarding. You will need admin access to your router to set this up. I recommend that you read that entire article because it probably applies directly to your situation.

3. Dynamic IP Address - most people still find it easier to work with IPv4 addresses - I won’t go into IPv6 right now, but you should read a little about it just for awareness. Your residential internet most likely has a dynamic IPv4 address, which means you can’t rely on that address staying the same forever (or even until next week), which means that you can’t configure your Cloudflare domain name to point to a single IPv4 address.

   Dynamic DNS is the solution for this, and again you’ll need admin access to your router to set it up.

4. HTTPS/TLS/SSL - if you get through all those issues then you probably have a working website, but now you’re seeing something like this when you try to view it in your browser:

   This doesn’t mean that you can’t get to your website - it just means that you can only do it via HTTP and not HTTPS, which the browser is warning you (and anyone else trying to view your website) is not secure. You can either just accept that this alert will always come up, and that you have to click through it, or you can learn about TLS and getting an SSL/TLS certificate. This is a later topic - it doesn’t matter and probably won’t make sense until after you’ve got your web server online.

I finally solved this problem in my desktop by having two separate M2 drives, one for Windows and one for Linux. Boot & grub live on the Linux drive and Windows never touches it.

With Linux and Windows on one drive, this is super annoying.

Run Qubes

Run whatever OS environment you need, in its own instance. Run a virtual networking stack. Crosslink your environments as needed. Segregate your environments as needed. Create new environments as needed. Destroy them as needed. Expand your virtual infrastructure.

Experiment with BSD and then realize that TrueNAS Scale is the last NAS environment you’ll ever need, and you didn’t really want to spend time on BSD anyway. Expand your server and network infrastructure.

Run every environment. Realize that you actually have a lot to learn about Windows, especially server and AD forests, and all the stuff you’ve complained about is actually kind of petty next to the monolith of professional computing environment that Microsoft has built (and also keeps making unnecessary self-harming changes to, and wtf is with user CALs anyway?). Learn to do user and domain management for real. Then learn what the real problems with Microsoft are.

Experiment with Redox, then give up and do something more useful with your time.

Install Xen Orchestra on some cheap secondhand Dell server you bought off eBay. Run a proper VM cloud environment. Run everything on top of it. Create your own VM golden images for the environments you use most often. Your personal computer doesn’t even have a local OS installed anymore, it’s just a terminal that runs whichever VM you need from your Xen server at the moment. Reject limitations.

OS elitism is for the weak and the simple. Enlightenment is understanding the strengths and weaknesses of each platform, and getting the best from all of them.

Development was dead for years, so dead that it wasn’t included in new release repositories

Clementine was a fork that was pretty good, but I think had more ambitions than active developers.

Strawberry later forked from Clementine and is still being developed, and they’re doing well, but they aren’t building on the KDE framework.