[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"term-c\u002Fcowboy-deploy":3,"related-c\u002Fcowboy-deploy":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fc\u002Fcowboy-deploy.md","Cowboy Deploy",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A cowboy deploy is pushing to production with zero checks — no CI, no review, no staging, just SSH into prod and let it rip. Sometimes it's heroic (3am outage, need to move fast). Usually it's reckless.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A cowboy deploy is a deployment made without standard process: skipping CI, bypassing code review, or pushing directly from a developer machine. It's acceptable only in genuine emergencies with senior approval and follow-up documentation. Normalized cowboy deploys indicate a broken deploy pipeline or culture problem.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Stop cowboy deploying. Write a runbook and fix CI.\" \u002F \"One cowboy deploy a year is fine. Weekly is a culture problem.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"devops","A cowboy deploy is pushing to production with zero checks — no CI, no review, no staging, just SSH into prod and let it rip.","beginner","md","c",{},true,"\u002Fterms\u002Fc\u002Fcowboy-deploy",[49,50,51,52],"Hotfix Friday","YOLO Deploy","Incident Response","Deploy Process",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fc\u002Fcowboy-deploy","HDpHdjoOJ9CrYsVSTA_vkMR5sJ-MhmfRCNNGzXW9BtA",[60,63,68],{"title":49,"path":61,"acronym":6,"category":40,"difficulty":42,"description":62},"\u002Fterms\u002Fh\u002Fhotfix-friday","Hotfix Friday is when your team decides 5pm on Friday is a great time to push an emergency fix. It's also how you end up working the weekend.",{"title":51,"path":64,"acronym":6,"category":65,"difficulty":66,"description":67},"\u002Fterms\u002Fi\u002Fincident-response","cicd","intermediate","Incident Response is the process your team follows when production breaks. Who gets paged? Who's the incident commander?",{"title":50,"path":69,"acronym":6,"category":70,"difficulty":42,"description":71},"\u002Fterms\u002Fy\u002Fyolo-deploy","vibecoding","A YOLO deploy is pushing code to production without testing it first because you're feeling brave (or reckless).",1776518270737]