You must log in or register to comment.
Stay borked, my friends.
The hero we deserve
Every team has a QA environment. The fancy ones have a separate production environment.
As a sysadmin, nothing makes me want to bitchslap devs harder. It’s shocking how many don’t even ask if we have a dev enviro. (The answer is yes)
My team made the “mistake” that all new projects need to be built and approved on our dev clusters before we allow them to be deployed to the prod clusters. We’re very explicit that dev is ephemeral, and that everything should be as code, so everything heals itself…
Despite this, whenever we reprovision the dev env, we always get emails from several different people saying that we wiped their prod databases and such. It’s crazy.
I stood up a test, staging, and prod pair of web server/dbs, got the Drupal 8 site stable on Drupal 10, hand it over, and yeah. No one uses anything but prod.
Thanks for 3x the work, ya dicks.
Only the lucky few have a test env separate to the production env.
My current job provided me with a test env that has half the resourse allocation of production, and it immediately runs out of RAM when you try to use it…
Mine is like 3 years out of date to prod.
this. the test environments we have need to be built manually and they haven’t been rebuilt in ages.
apparently it was a multi month project to get it setup in the first place. nothing like trying to recreate a bug in dev and finding out there’s 1000 lines of different code in the sandbox (that’s also misbehaving but in new and fascinating ways)
I use a sample for tests, not the full set
test? just do it and let your uptime kuma alert tell you if something’s wrong.
that’s the test
Production? That’s just our pool of thousands of testers who pay for the privilege!
Tested in the school of hard knocks.
Check for security vulnerabilities? But Internet hackers will do that for free.
I literally live between ops sentiment and this sentiment
I stand shit up as a test server and then threat model before cloning a production server to a separate vlan and lock it down proper, with the added Intel of a snapshot on how the test server got tested.
