It's possible for a while but there is a whack-a-mole game if you're doing anything they would care about. So you will have to keep moving it around. VPS forums will have some info.
I see a few on the road or parked now and then. I cringe every time.
I sometimes think that for a future vehicle I might like to do an EV conversion on an older gas burning, small SUV. Now suddenly I struck by the idea of an EV to EV conversion, to get rid fo the Tesla computers full of spyware. It would still be recognizeable though, not good.
I was just looking through old books and noticing my Yggdrasil manual the other day. That was one of the earliest plug and go cd-rom distributions. Before that was e.g. Slackware and the early Debian, both of which involved big piles of floppies. I also remember sending Linus an email and getting an answer. I'm sure he is too much of a busy celebrity for that now.
It’s a research reactor, it will be relatively small because it’s not intended to provide a production power source.
I get that and a research reactor is a fine thing, but I'd like to have gotten some info about the scaling potential. Like are there obstacles to large scale utility power being generated with thorium?
Unless Van Hollen brought back fingerprints or a DNA sample, or the family got to talk to the guy on the phone and confirm it was him, I have to keep open the possibility that Bukele put in an imposter.
Oh I didn't know about the new requirements. Less backwards compatibility too. IBM 3592 looks better but costs even more. Tape drives can't be that much higher tech than HDDs, so if they cranked up the volume they could likely be way more affordable.
The upfront cost of tape is excessive though. It wasn't always like that. And LTO-9 missed its capacity target: it's 18TB (1.5x LTO-8) instead of 24TB as planned. Who knows what will happen later in the roadmap.
I'm still driving mine and would be very reluctant to swap it for a modern enshittified car. I sometimes think of homebrewing my next car (DIY EV conversion of an older ICE car) rather than put up with any manufacturer's offerings. Who knows.
Noo, really, idk what Disco was but tags and recommendations from other humans are plenty to find good AO3 fic to read. And AO3 itself has been getting hammered for months, presumably by corporate AI crawlers. A recommendation engine would also have to crawl AO3. That's very difficult to do because of said hammering. Even the regular download feature barely works now if you use fanficfare for it.
Scroll to the part about server side hooks. The idea is to automatically propagate updates when you receive them. So git-level replication instead of rsync.
I see, fair enough. Replication is never instantaneous, so do you have definite bounds on how much latency you'll accept? Do you really want independent git servers online? Most HA systems have a primary and a failover, so users only see one server. If you want to use Ceph, in practice all servers would be in the same DC. Is that ok?
I think I'd look in one of the many git books out there to see what they say about replication schemes. This sounds like something that must have been done before.
Why do you want 5 git servers instead of, say, 2? Are you after something more than high availability? Are you trying to run something like GitHub where some repos might have stupendous concurrent read traffic? What about update traffic?
What happens if the servers sometimes get out of sync for 0.5 sec or whatever, as long as each is in a consistent state at all times?
Anyway my first idea isn't rsync, but rather, use update hooks to replicate pushes to the other servers, so the updates will still look atomic to clients. Alternatively, use a replicated file system under Ceph or the like, so you can quickly migrate failed servers. That's a standard cloud hosting setup.
What real world workload do you have, that appeared suddenly enough that your devs couldn't stay in top of it, and you find yourself seeking advice from us relatively clueless dweebs on Lemmy? It's not a problem most git users deal with. Git is pretty fast and most users are ok with a single server and a backup.
I wonder if you could use HAProxy for that. It's usually used with web servers. This is a pretty surprising request though, since git is pretty fast. Do you have an actual real world workload that needs such a setup? Otherwise why not just have a normal setup with one server being mirrored, and a failover IP as lots of VPS hosts can supply?
And, can you use round robin DNS instead of a load balancer?
It's possible for a while but there is a whack-a-mole game if you're doing anything they would care about. So you will have to keep moving it around. VPS forums will have some info.