On Jul 12, 2010, at 9:50 AM, Nils Breunese wrote: > Yeah, even http://couchapp.org/ says > {"error":"insecure_rewrite_rule","reason":"too many ../.. segments"} >
we just upgraded that couch to 1.0. I will deploy new code I hope before lunch today. Chris > Nils. > ________________________________________ > Van: Martin Hilbig [[email protected]] > Verzonden: maandag 12 juli 2010 18:45 > Aan: [email protected] > Onderwerp: Re: publicly replicable couch app needed > > sadly all your links give me a: > > { > error: "insecure_rewrite_rule" > reason: "too many ../.. segments" > } > > have fun > martin > > On 12.07.2010 17:30, J Chris Anderson wrote: >> >> On Jul 12, 2010, at 7:58 AM, Ning Tan wrote: >> >>> Hi all, >>> >>> I'm giving a short presentation on CouchDB replication to my >>> colleagues and would like to demonstrate the "application is >>> document" aspect. Is there any good, publicly replicable couch apps >>> out there? I'd like to give it a try. >>> >>> Thanks a lot. >> >> >> Here are a few: >> >> http://couchapp.org/focus/_design/focus/index.html#/focus >> >> http://couchapp.org/photo/_design/proto/index.html >> >> http://couchapp.org/tapirwiki/_design/tapir/wiki.html#FrontPage >> >> And this one is crazy but could be made awesome with more work. >> >> http://couchapp.org/ice/_design/ice/index.html >> >> I hope others add their own to this list. >> >> I have a "Garden" app here: >> >> http://couchapp.org/garden/_design/garden/index.html >> >> It can be a bit challenging to get design documents to replicate. (It can >> help to put the target couch in admin-party. I really hope this is fixed in >> 1.0...) >> >> If there are ddoc replication issues you can use `couchapp clone` and push >> to do it. >> >> Cheers, >> Chris > > De informatie vervat in deze e-mail en meegezonden bijlagen is uitsluitend > bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke informatie > bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking > van deze informatie aan derden is voorbehouden aan geadresseerde. De VPRO > staat niet in voor de juiste en volledige overbrenging van de inhoud van een > verzonden e-mail, noch voor tijdige ontvangst daarvan.
