

That’s it. Been a long time since I had to use that and I found it had it’s issues so I moved to the qdevice without a third node.
That’s it. Been a long time since I had to use that and I found it had it’s issues so I moved to the qdevice without a third node.
If I remember right, the Kodi addon for Mediatracker doesn’t work, which would be a dealbreaker for me as we watch everything via Kodi debrid addons.
It’s not Nix-specific, but I use Mailcow-dockerized and it is completely hassle-free, been using it for 4 or 5 years now without a bobble (though I’ve run my own mailserver for 30 years).
I would agree that a static IP is necessary, but I don’t have one and I get by, even without a PTR record. That’s probably due to a fairly small ISP with not many spammers having found it.
Make sure you set up your DKIM and DMARC right from the start and pay heed to the reports. But I’ve never had to fight to get off a blacklist, even with new domains I’ve added to it.
Yes. You can just get by with 2 devices but you need to set expected_votes=1 in the cluster config somewhere, don’t recall where, and I’ve encountered issues with stability with that solution, seems like it’ll get undone though I haven’t used it for years to say if that’s still the case.
The q-device will work on anything Linux that’s available when the second node is down. Not having the tie-breaker isn’t the end of the world, it just means you have to go in after you bring up the second node and start some things manually, and if you’re replacing nodes in a 2-node cluster, it’s much nicer to have the q-device.
Proxmox uses a voting system to keep cluster integrity.
Check it out, it’s free and does a lot of things out of the box that take a lot of manual work otherwise. And the backup server is stellar. It does take a while to wrap your head around the whole way it does things, but it’s really powerful if you spend the time to deep dive it.
It works well. I have my docker hosts on HA as well because they’re almost as important as the router.
If you just use 2 nodes, you will need a q-device to make quorum if you have one of the nodes down. I have the tiebreaker running on my Proxmox Backup Server shitbox I3.
Proxmox is basically just debian with KVM and a better virt-manager. And it deals with ZFS natively so you can build zpools, which is pretty much necessary if you want snapshotting and replication, which are necessary for HA.
I run OPNsense on a 2 node proxmox server and have for a few years now. I have HA set up and have had it fail over gracefully when I’ve been away and not even noticed it having failed over for more than a week. If I want to upgrade it, I snapshot it, and if I upgrade the host I live migrate it, and I’ve done this all remotely more than a few times with no issues.
It takes some planning and I’d say you’d want a cluster (at least a pair of nodes) where you can do HA. But I wouldn’t do it any other way at this point. If you have only one port, you can VLAN it for using on both LAN and WAN.
Was it 4? I thought it came around for the 5 release. I think I switched DEs for almost the entire 4 debacle then switched back at 5 when it stopped sucking.
Edit: NM, I see I just missed it by skipping 4: https://dot.kde.org/2009/11/24/repositioning-kde-brand/
If you’d done a docker commit on your earlier changes, they’d have stuck as well.
The proper way to do this is to fork their image project and alter the nginx files that get incorporated in the build. Then you can run the stack with a build command instead of an image reference, and git pull your fork whenever there’s upstream merges. Or Action the fork to build an image for you every time it gets merged that you reference in your docker compose instead.
deleted by creator
Foreign and corporate. Anything over $2000 from an entity.
This might be the last chance to migrate from Gitea to Forgejo and avoid whatever trainwreck Gitea is heading for. It’s going to a hardfork soon.
It’s all automated now, it’s pretty hard to mess up a standard install. It’s not like the good old days.
I’ve used Joplin for years. IDK why people have a hate on for it, it’s fine.
If you’re the type of person (like me) that can name at most 4 colors, then you don’t care.
I guess on the rare occasions you need to specify the driver, this is the answer. Otherwise, it’s a lot of extra work for no real benefit.
I like having everything to do with a container in one folder, so I use ./ the bind mounts. Then I don’t have to go hunting all over hells half acre for the various mounts that docker makes. If I backup/restore a folder, I know I have everything to do with that stack right there.
The Qidi machines will do CF filaments. There’s been a few discussions on here about them.
They’re like an opensource version of the Bambu, and they’re supposed to be putting out a multicolor box system soon. They’re running Klipper.
For just an AP, I’ve used a number of the GL-AR300 and they’ve been fine as AP and repeaters, but only 2.4 GHz. I have no interference issues where I am so that’s fine for me, but if you’re somewhere populated, YMMV.
They also have the full firewall/router set on them, but I generally don’t use them for that.
I live in rural AB and I’d be surprised if 1 person in 10 had anything good to say about trump. Most people know that he’s a lying shitbird, and want nothing to do with him. And frankly Danielle Smith is sliding fast since her toadying reaction to his tariff threats.