database - Changing code on a production server is evil: But what's the best way to handle it, if you do it? -


changing code on production system quick-fix problem seductive. if know it's evil , bad , dangerous - day comes ignore facts , nevertheless.

for of go dark side time time: how try fix drawbacks? install svn (...) server track changes on prod machines? install job compares checksums of files , sends out "remember-you-changed-this"-mails? place note on whiteboard? sync changes development server?

added: take fact kind of bad practice happens. not interested in perfect workflow avoid this. or whether happens more in php or java or cobol projects. or in small vs. big projects. in newbie vs. veteran projects. or if punished cosmic entity if it. interested in creative usable tips people know how handle kind of situation.

have rollback plan in case quick fix doesn't work.

for website, may simple copying whole thing backup folder.

often, entails having database script undo changes made in database scripts.

have smoke test can tell if have broken application.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -