Use object storage for media and backups, then use s3 replication to put a copy somewhere else.
Use object storage for media and backups, then use s3 replication to put a copy somewhere else.
Get a second pc and a kvm switch
I’d wreck you at KI noob
Archlinux
I did 100TB, 100 streams of 1TB, all simultaneous with rsync
Red Hat, because it’s free for developers and used by a lot of enterprises.
If you have enough users and systems that this is a problem then you should be centrally managing it. I get that you want to inventory what you have, but I’m saying that you’re probably doing it wrong right now, and your ask is solved by using a central IAM system.
It sounds like you’re probably looking for some kind of SAML compliant IAM system, where credentials and access can be centrally managed. Active Directory and LDAP are examples of that.
I have a Bug A Salt Home and Garden edition and I love it. I’m in a dry climate though, so the salt doesn’t clump up. Mileage may vary if you’re in a humid place.
The person who bought the cottage next to my parents lived in the same neighborhood I was living in, 4600km away. She was just some random person who bought it.
Well, 1ms of latency is 300km of distance, so unless you have something really misconfigured or overloaded, or you’re across the country, latency shouldn’t be an issue. 10-20ms is normally the high water mark for most synchronous replication, so you can go a long way before a protocol like DNS becomes an issue.
Realize that the person who rejected you is the wrong person, since why would you want someone who doesn’t want you? Dodged a bullet there
I find a lot of stuff is using docker compose, which works with Podman, but using straight docker is easier, especially if it’s nothing web-facing
Yes, but you don’t need Kubernetes from the start.
Use object storage and enable immutability for the backups. If they compromise your site they shouldn’t be able to delete your backups unless they have the NAS password too.
Script that checks your external IP and updates your DNS provider via API.
Read books about how to negotiate. You can stand on the backs of giants. I’d start with “How to win friends and influence people” by Dale Carnegie, as it’s a good guide on how to just deal with people.
Why replace Hashi if you’re in the RH or IBM ecosystem? Why replace it at all if you’re an enterprise? They have enterprise support.
There’s not much cost with S3 object. It’s just a file system in Linux, and replication is a protocol standard.