So... you were doing a production redeploy, and it crashed?<p>The URL &quot;git:&#x2F;&#x2F;github.com&#x2F;components&#x2F;ember.git&quot; [1] suggests this is an internal GitHub Bower build log, but your post history doesn&#x27;t mention anything about GitHub (let alone whether you work there), so I&#x27;m not 100.00% sure.<p>[1] <a href="https:&#x2F;&#x2F;webcache.googleusercontent.com&#x2F;search?q=cache:3e00jlTZDzoJ:https:&#x2F;&#x2F;github.com&#x2F;components&#x2F;ember" rel="nofollow">https:&#x2F;&#x2F;webcache.googleusercontent.com&#x2F;search?q=cache:3e00jl...</a><p>Assuming this is, in fact, a GH Bower log, the first thing that came to mind was that this architecture isn&#x27;t (and possibly should be) using a dual-silo approach: when you upgrade, the upgrade gets loaded into a new blank namespace&#x2F;environment, tested, and if it worked (passes CI test coverage or something like that), the main entry point is switched to the new environment (maybe with a web server restart or config rehash) and the old environment gets purged (possibly after a trial period). The current stack looks quite akin to &quot;click this button to flash the new firmware and DO NOT UNPLUG your device or you&#x27;ll brick it.&quot;<p>But then I realized... wait. You guys have like... isn&#x27;t it like, a few dozen RoR worker boxes? Was this crash on the inbound router or something? xD<p>It&#x27;s all good though; consider this &quot;curious criticism&quot; - like constructive criticism, but with extra sympathy. And hey, GH&#x27;s never broken on my watch before (not that I need it atm... hopefully); this is interesting =P