30.11.2011 22.48, Dave Cottlehuber kirjoitti:
On 30 November 2011 16:23, Zachary Zolton<[email protected]> wrote:
Niklas,
The best way I have found to deal with this is to add these steps to
my deployment procedures:
* push the new design doc as _design/your_ddoc_name-prime
* query any view from that _design/your_ddoc_name-prime with ?limit=1
* wait for the view query results
* push the new design doc again as _design/your_ddoc_name
* finally, switch over to the new version of your application code
This doesn't require any special knowledge in your clients, since they
always query _design/your_ddoc_name.
I've used this approach several times and it works like a charm. Yes,
you'll have to write a small script, but it's really not that bad.
--Zach
It's so short I don't think anybody saw a need to write a separate tool for it.
http://wiki.apache.org/couchdb/How_to_deploy_view_changes_in_a_live_environment
A+
Dave
Hi, thanks for your reply.
In my case I guess I need a dedicated tool, as I have setup filtered
continuous replication for "per-environment" databases.. But shouldn't
be hard to make a threaded tool for design document management. Thanks
for the pointers!
Niklas
