Every team has a QA environment. The fancy ones have a separate production environment.
this post was submitted on 30 Jul 2026
135 points (97.2% liked)
linuxmemes
32260 readers
1236 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
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.
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!
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.
I use a sample for tests, not the full set
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.