![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://sh.itjust.works/pictrs/image/045a2049-eb61-4960-88ba-97e7f1ffbf31.jpeg)
I think this is just an excuse to delay it. I don’t think there’s that many big releases coming up this year.
I think this is just an excuse to delay it. I don’t think there’s that many big releases coming up this year.
I mean disaster planning is about finding ways to mitigate things like power or internet going down to minimize or eliminate their impact. That said, accepting the risk of downtime because alternatives are too expensive is a perfectly valid decision as long as it’s an intentional one.
15 year old game at this point
There isn’t really a direct equivalent. AD is a great product. Best to focus on the individual pieces instead of the whole package for a replacement.
“Review bomb” aka getting bad reviews.
What you’re asking for is a CI/CD pipeline that deploys a set of OS updates as a set revision. I don’t the details on how to do it but that’s the concept you’re asking for.
Use a CI/CD pipeline with a one box and preprod and run service integration tests after the update.
I’m sure it’ll be airgapped and completely separate from the rest of AWS.
That’s why you build it in Australia and only give Australian citizens with appropriate security clearances direct operational access.
You’re just irrationally disliking it based on the name “AI” and nothing factual.
I think that sounds like a cool use case. If it runs locally what’s not to like?
Yep, no one claimed otherwise.
Yes, you create virtual nics tied to the physical one.
In larger networks VLANs let you do network segmentation across switches, which you can’t really do otherwise.
I wouldn’t bother at home.
Personally I’d probably go with MS hosted exchange or a Google business account. If you don’t trust those entities I’ve heard good things about ProtonMail - I imagine they have some kind of business solution.
Buy your own domain name and put it in front of someone else’s service. This is going to be a ton of work to do correctly and you’re unlikely to be able to host it out of your house.
Also, something you’re running off a Raspberry Pi in your house is not going to meet most definitions of ‘reliable’.
Many ISPs will also block inbound SMTP unless you have business account (and sometimes even then) because it’s a common malware/spam vector.
If you insist on going through with this the key thing is to make sure that you’re not an open relay.
100% agreed. It’s well worth outsourcing to someone else for $10/mo versus the amount of work it takes to do it well unless you’re a large business.
I’d make this argument for DNS too - a lot of work for how easy it is to pay someone else to handle it.
Yeah, in which case you wouldn’t accept the downtime and would drop the cash on redundant systems.