It’s perfectly fine for some private page etc. but when you make business software for customers that require 99,9% uptime with severe contractual penalties it’s probably too wonky.
It’s perfectly fine for some private page etc. but when you make business software for customers that require 99,9% uptime with severe contractual penalties it’s probably too wonky.
We got our own platform based on kubernetes and cncf stuff and we don’t have to care anymore about the metal underneath. AWS? OTC? Azure? Thats just a target parameter, platform does the rest. It’s great.
People do this all the time.
When you handle all your errs the same way, I’d say you’re doing something wrong. You can build some pretty strong err trace wrapping errs. I also think it’s more readable than the average try catch block.
Oh I didn’t know about the priority system. That might help. I guess I’ll try to figure out, if I need the wolfi repo in the first place and remove it if possible and in addition add OpenSUSE as a vendor of higher prio to avoid similar issues in the future.
I need the colored one as a sticker to cover that weird square thingy on my super keys.
It’s not about switching, it’s about hosting our services on different platforms at the same time.