StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>(That is quite a few questions inside one big question.)</p> <p>But I would refer to the Continuous Delivery book <a href="http://rads.stackoverflow.com/amzn/click/0321601912" rel="nofollow">http://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912/</a></p> <p>Edit: (As commented you already read this book) Some suggestions which you may already do, but for others with similar issue:</p> <ul> <li>Ensure less coupled interfaces by using <a href="http://en.wikipedia.org/wiki/Duck_typing" rel="nofollow">duck typing</a>. </li> <li>Use <a href="http://martinfowler.com/bliki/FeatureToggle.html" rel="nofollow">feature toggles</a> to gradual roll out of features across your inter-dependant applications.</li> <li>Evolution scripts for the DBs</li> <li><a href="http://blog.cherouvim.com/a-table-that-should-exist-in-all-projects-with-a-database/" rel="nofollow">Version table in every DB</a></li> <li>Symlinks is a neat way of toggling rollouts of standalone apps</li> <li>Have a look at how other big enterprises rollout: <ul> <li><a href="http://news.ycombinator.com/item?id=411282" rel="nofollow">Amazon use of new server per deployment</a>:</li> <li><a href="http://vimeo.com/28795465" rel="nofollow">Netflix build demo by Carl Quinn</a> using short lived cloud instances</li> <li><a href="http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/" rel="nofollow">50 times a day at IMVU</a> and <a href="http://www.startuplessonslearned.com/2009/06/why-continuous-deployment.html" rel="nofollow">blog by Ries</a></li> </ul></li> </ul> <p>But I have no solid solution to the inter-dependency auto-deploy strategy you actually ask for :|</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload