I got a mini pc (e.g. a NUC). I did this after the price for rasps went sky high. Check out used NUCs, you can get a lot of power for the price.
I got a mini pc (e.g. a NUC). I did this after the price for rasps went sky high. Check out used NUCs, you can get a lot of power for the price.
I backup Proxmox VMs and templates onto my NAS, and from there into the cloud. If you don’t want the cloud maybe auto backup to an external drive and keep it somewhere safe (out of range of a possible disaster to your home)
They don’t really care why, just don’t say anything that trashes your current employer or makes you look bad.
I went with a Synology and have been very happy with it. Easy to use, very nice GUI, yet quite powerful with the features provided.
From there I moved on to NUC. I used to host several things through Docker on the Synology but I’m now moving many of those things to the NUC.
I have a 5g home internet backup connection. My primary internet is fiber, so my thinking if there is a cut somewhere it could also affect cable, so I use over the air as my backup.
Having the e2e smokes be a requirement for PR merge is frustrating. But I’ve been on the fence before with this on my own teams. It’s enticing to have a completely “clean” main branch that has not been infested with regressions caused by a PR.
It also gives you confidence in the crummy cases where you need to push a fix to prod right now.
If the e2e’s flap too much, then it is not an option. I’ve tried it and it lasts one sprint before we nix it. It’s just too frustrating and development comes to a standstill.
We have a retry policy on any smokes that need to run in a step by step order, and we aggressively prune and remove smokes that frequently fail or don’t test for real issues.
I actually think that’s the best way to handle it.
Who fixes the issues that the smokes find?
On teams I’ve been on, typically a junior dev. Sounds crummy, but it actually gives them more experience with the product/code. I have been that junior dev before and I found it a positive experience.
Ugh, what a mess. Thought about this for a while today and three thoughts started circulating in my head:
Hire an actual lawyer and get firm legal advice on this issue. I think this would fall to the admins, not the devs. Maybe an admin who wanted could volunteer to contact a lawyer? We could do a gofundme for one-time consultation legal fees.
Stop using pictrs completely and instead use links to a third party such as Imgur or whatever. They’re in this business and I’m sure already have dealt with it and have a solution. Yes it sucks that Imgur (or whatever third party) could delete our legitimate images at any time, but IMHO it’s worth it to avoid this headache. At any rate it offloads the liability from an admin. Of course, IANAL and this is a question we would want to ask a lawyer about.
Needing a GPU increases the expenses for an admin significantly. It will start to not be worth it for quite a few to keep their instance running.
Thanks for bringing up this point. This is obviously a nuanced issue that is going to need a well-thought-out solution.
I was thinking the same thing. Stop storing the images and offload to Imgur or whatever. They likely already have a solution for this issue. Show images inline instead of a link. Looks the same, no liability.
Saying that, this is tremendously cool. I was given pause though by another poster on the thread mentioning the legality of using this in the U.S.
LMAO. So, so true and I have no problem with it. Self-hosted seems to be one of the most active communities on Lemmy. I learn a lot and y’all all seem cool.
Nope. I’ve used AWS, Digital Ocean, and Backblaze. Never any problems.
News like this, and the 3DS store closing down, is why I purchase physical media for my games.
I wouldn’t call this guy a top physicist… I mean he can say what he wants but you shouldn’t be listening to him.
Yeah I don’t see how he has any time to be a “top physicist” when it seems he spends all his time on as a commenter on tv shows that are tangentially related to his field. On top of that LLM is not even tangentially related.
In fact, by the time the crash happens, it’s alerted the driver to pay more attention no less than 150 times over the course of about 45 minutes. Nevertheless, the system didn’t recognize a lack of engagement to the point that it shut down Autopilot
I blame the driver, but if the above is true there was a problem with the Tesla as well. The Tesla is intended to disengage and disable autopilot for the remainder of the drive after a small number of ignored alerts. If the car didn’t do that, there’s a bug in the Tesla software.
I think it’s more likely the driver used a trick to make the car think he was engaged when he was not. You can do things like put a water bottle wedged in the steering wheel to make the car think you have tugged on the steering wheel to prove you are engaged. (Don’t ask me how I know)
There is no functionality in the interface so there is nothing to test. You test the logic of the implemented methods.
With that said, with reflection you can at least test that an interface has the right method names and annotations present, but I’ve extremely rarely found it useful to do so.
Besides the CPU how was the other resource usage on your VPS? Like memory, storage, etc
Facial recognition by law enforcement should be banned.
Nice. What do you plan to do with it?
@lengsel@latte.is not.coffee I did not, super interesting.
Are there advantages to this over self hosting Vaultwarden?