Buckshot

joined 1 year ago
[–] Buckshot@programming.dev 3 points 4 weeks ago

Definitely. What I didn't mention is all that took over a month!

[–] Buckshot@programming.dev 11 points 4 weeks ago (2 children)

Been there many times. Had one case where support had to through the reseller who sold licenses in our country. Actual people who knew what they were talking about was tier 3.

We had a bug and were trying to report it and get a fix or workaround. Just told no, we're doing it wrong. After a lot of back and forth we had to pay for an "expert" to fly over and show us what we were doing wrong. Turns out he wasn't an expert, he was a salesmen. Made a demo for us on the flight and the first time he ran it was in our meeting room on projector.

Failed in exactly the way we had been saying. It was very satisfying.

Finally he phoned the dev team who confirmed the docs were wrong and we couldn't do what we were trying.

[–] Buckshot@programming.dev 1 points 5 months ago

I use restic but I switched from Borg because of the cloud features. Outside of that, there's not a lot of differences really. If you're happy with Borg keep with it.

 

We're using Terraform to manage our AWS infrastructure and the state itself is also in AWS. We've got 2 separate accounts for test and prod and each has an S3 bucket with the state files for those accounts.

We're not setting up alternate regions for disaster recovery and it's got me wondering if the region the terraform S3 bucket is in goes down then we won't be able to deploy anything with terraform.

So what's the best practice for this? Should we have a bucket in every region with the state files for the projects in that region but then that doesn't work for multi-region deployments.