I lol’d out loud irl
I lol’d out loud irl
It’s lighter than a VM but a bit heavier than aiming to run an application natively (and all the dependency & configuration hell that entails).
Basically a convenient way to package and run applications with all their dependencies, without regard for what libraries & configurations exist in the host OS and other containers.
If your application only works with up to version 42 of the Whatchamacallit library, you ship it with that version of Whatchamacallit, the underlying OS doesn’t need to install it. Other containers running on the system that depend on that library don’t get broken since they’re packaged with version 69 which works fine for them.
Meme answer:
Pressing F to pay respects. R.I.P. in pieces
Depending on how mission critical your data is…Set up delayed replicas and backups (and test that your backups can actually be restored from). Get a second pair of eyeballs on your query. Set up test environments and run it there before running it in production. The more automated testing you put into your pipeline, the better. Every edit should be committed and tested. (Kubernetes and GitLab Auto DevOps makes this kind of thing a cinch, every branch has a new test environment set up automatically)
Don’t beat yourself up too much though. It happens even to seasoned pros.