I have no issue with corporate funding. I have an issue when a company gets to make all the decisions. Lot of good software has gone to hell when the shareholders need profit now instead of seeing a long term vision.
We’ll see, but I’ve been around this rodeo enough to just avoid it from the start and take some pain now instead of putting in effort that’s going to be wasted later.
2023, I remember the announcement last year. Not sure where you’re getting 2014 from, that was even before NC split off.
What puts me off of Owncloud is the new ownership. I couldn’t care less if it’s written in the blood of Christ, if I have to worry about the rug getting pulled out from under me for self-hosting, it’s a no-go for me, Joe.
Nextcloud works well for me and has for years. The people that don’t like it can go use this, and we’ll see you back in a couple of years when it goes open-core or worse.
If you can cool the garage, insulating the ceiling will help. Even if you run a fan to pull in cool air at night and then try to hold it in, it’ll help.
Probably depends on the ISP, but I just have 2 nics in each server, and eth1 on both is on a switch to the cable modem. If one goes down, the other comes up fine. Can’t recall if I spoofed the same MAC on the OPNsense VMs.
VMs under KVM are pretty much bare metal and Proxmox doesn’t use much for resources itself, it’s basically a headless Debian with a webserver interface to do all the KVM stuff.
Proxmox, especially if you use ZFS for the VM datastore, makes a home lab so much easier to revert, backup and deploy/clone VMs and LXCs. I highly recommend it if you’re just starting out. Once you wrap your head around it, it gets out of the way and lets you just tinker with your projects, and not have to manually do everything in VirtManager or at the command line.
Combined with Proxmox Backup Server, it’s a production ready hypervisor for anything you decide to keep. Also, the HA features work well enough that I had my main routing OPNsense VM jump between nodes when the primary node lost a drive, and I didn’t notice for a week, it was that seamless.
As to why distro maintainers go along, if you had to vet every time the network stack updated and make sure it doesn’t break your custom solution to predictable naming, you’d probably just go along with it and let anyone that needed it devise and maintain their own solution. 99% of users won’t worry about it.
Use a firewall like OPNsense and you’ll be fine. There’s a Crowdsec plugin to help against malicious actors, and for the most part, nothing you’re doing is worth the trouble to them.
The hero we need.
My god, that was 15 years ago.
IDK, I’ve found Gnome unusable for a long time. I tried to make up for it with extensions for a while, but every release would unapologetically break something I found essential and the extension devs would give up trying to keep them going.
I understand that eventually they got better about dropping breaking changes without warning, because extension devs were leaving in droves, but at that point KDE got good again with Plasma, and I’ve never looked back.
Gnome has their vision to be a completely hands off, dumbed-down, unbreakable DE for the lowest common denominator. I guess judged by that light, it’s a success. It’s the default in a lot of distros because it’s low maintenance for packaging and support. Frankly, I think it’s a major reason for the slow speed of Linux desktop uptake, but what do I know.
Gnome devs judge release success by the amount of features they managed to remove since last release and make it easier to maintain.
Eventually it’ll be one button in the middle of the screen that turns it on and off.
Memes are srs bidness.
It’s Linux, not Unix.
Grab your ankles and bite the pillow, Microsoft is going in dry.
While there’s probably a better way of doing it via the docker zfs driver, I just make a datastore per stack under the hypervisor, mount the datastore into the docker LXC, and make everything bind mount within that mountpoint, then snapshot and backup via Sanoid to a couple of remote ZFS pools, one local and one on zfs.rent.
I’ve had to restore our mailserver (mysql) and nextcloud (postgres) and they both act as if the power went out, recovering via their own journaling systems. I’ve not found any inconsistencies on recovery, even when I’ve done a test restore on a snapshot that’s been backed up during known hard activitiy. I trust both databases for their recovery methods, others maybe not so much. But test that for yourself.
Snapshot with zfs, backup snapshot.
Really, this looks fine. I’ve seen a pile of metal roof in rural ag areas, and this is the right boot, done the right way. Yah, if they’d thought ahead they might have been able to schedule the sheets to not land on the seem. But putting the boot at 45* and screwing them on either side of the seam is correct, though that bottom one is squonky, but it’s at the bottom so it shouldn’t be an issue. Proper caulking under and around. This is probably as good as it gets.
I usually see these at that angle, supposedly so it sheds water to either side instead of damming it by being horizontal. Metal roofs are pretty common in rural areas, and the boots are done like this.
Honestly, this doesn’t look bad.
Jellyfin is basically a storage/streaming server. You still have to get the files, which is where Sonarr/Radarr/QBT come in.