On 11/15/06, Timwi timwi@gmx.net wrote:
Brion Vibber wrote:
- Have a read-write configuration using live data with alternate new
code. Potentially very unsafe.
It would be "potentially very unsafe" only if you place completely untested code on it. I thought the idea was to place code on it that would otherwise have already gone out to the live site. Surely it's much safer to beta-test it first than to push it live immediately. In other words, I see it as an _addition_ to the development process you are already using, and it would catch problems such as the CSS/JavaScript one you mentioned before it goes live.
I was hoping that there was a clear enough boundary between "database interaction stuff" and "other wiki code" that we could perhaps update the other stuff without touching the (potentially harmful) database interaction stuff. But sifting around the source a bit is making me more nervous about that.
Operationally, how do you handle it if you do upgrades that require database changes? What are the existing DB upgrade and rollback procedures?
Thanks.