That’s actually easy.

The shape of the district gets decided based on the concentration of votes for one party. The goal is to make enough districts with enough concentration of your voters that you always win those districts, and make the rest of the state have few enough districts with enough of a mix of of voters for both parties that A) the for-sure districts can’t be lost and B) the not-for-sure districts can never oppose the for-sure districts as long as they remain under your party’s control.

So all the rigging party needs to do is campaign enough in the for-sure districts that they can’t lose, and campaign enough in the not-for-sure districts that their opponent can’t win. And then because of the Electoral College, all of the states votes go to the rigged party.

I can’t do shit about that in Pennsylvania. You’d think there would have been more an effort to disprove the allegations or fix the problems sometime between 1865 and now.

I use Nextcloud for contacts, calendars, files, bookmarks, passwords, to do lists, Kanban boards, and recipies. You absolutely can turn nextcloud into a 365 competitor if that’s your jam

You might want to set up dynamic DNS for your domain. If you’re hosting from a residential internet connection then your ISP will change your address eventually. Ddclient can be used to report your current IP to your Registrar regularly, so if it changes the domain moves along with it.

Build is solid, but here’s some suggestions.

1. Another 8TB HDD. the reason being you can merge the 4 drives of the same size into a RAID5 array for data redundancy.
2. An SSD to install the OS on.
3. (Optional) More RAM check the mobo to see the max size and speed it can handle, and then fill every slot with that.

I tried Joplin for a while but dropped it, too simple. Also tried Trilum, which I liked more but it’s still a very young project.

Eventually, my Obsidian vault will go there, but not just yet.

Rather than give you specific recommendations, here’s some guidance for parts

Mobo: The more slots you have for RAM and storage, the better.

CPU: literally anything. More cores and faster cores are ideal, but CPU requirements for these things are generally lower than a desktop.

RAM: Buy 1 stick of the fastest and highest capacity RAM your motherboard can handle. When you’re ready or you start to see slowdown, buy another of the same stick. You can get far on 16-32GB, you won’t need much more until later.

Storage: an SSD for the OS and one or more HDDs for storage.

PSU: generally anything in the 500-700 range will be good. You’ll want more if you plan to put a GPU in, though.

The Titanic chose a new Captain today after the humiliating iceberg incident, insists we have not taken on too much water and pleads for unity aboard the sinking ship.

Speaking of where we’re talking on just now, Lemmy support in general would be great too. Not sure but I assume your suggestion would mean the same thing?

So CosmOS does run through Compose files, but it makes them on the fly and gives you a moment before runtime to review it and make any changes.

Am I understanding right that your idea here is to put the Volumes on the NFS share and run through that, as opposed to having the data outside of a Volume just sitting on an NFS Mount?

I’m still early enough in that if something’s wrong or not ideal about the config, I can go scorched earth and have the whole thing back up and running in an hour or two.

Is there a better filesystem that I could share out for this kind of thing? My RAID Array is run through OpenMediaVault if that helps.

That tracks with my experience as well. I’ve been trying to get a system set up where the OS and Docker live on a small disk by themselves, and then go out to the larger RAID Array to load its data. But it’s sounding like that’s not really going to work the way I want to (probably why it’s crashed on me so many times, too).

So I have a 2TB nVME for VM Host Disks, and a 72TB RAID Array on my server. My hope is to have the OS and Docker on the 32GB drive I set up for the VM (which lives on the nVME), and then all the files related to the webapps live in a folder on RAID Array in a section meant just for that.

But the other responses in this thread make me think that’s not really going to be an option. Maybe I could make a very large VM Host Disk and put it on the RAID Array, let Docker just forget about the mount points entirely…

Just one more tax break will fix everything, I’m sure of it!