Hello,
For some time I am struggling with getting the BrowserId (Persona) plugin
running on my machine (OSX Mavericks).
Previously I compiled https://github.com/iriscouch/browserid_couchdb using
`rake plugin=git://github.com/iriscouch/browserid_couchdb origin/master”` on
build-couchdb. For
On 18. Dezember 2013 at 11:09:56, Sjoerd de Jong (sjo...@weett.nl) wrote:
Hello,
For some time I am struggling with getting the BrowserId (Persona)
plugin running on my machine (OSX Mavericks).
Previously I compiled https://github.com/iriscouch/browserid_couchdb
using `rake
Futon on Apache CouchDB 1.2 (according to Futon)
{couchdb:Welcome,version:1.2.0} according to ?
CouchDB 1.4.0 Ubuntu according to Package name
I set os_process_timeout 50 (effective infinity).
I ALWAYS get the VERY unhelpful message which merely prints the document
contents.
Hello,
I have a question regarding the ETag generation of CouchDb.
Our setup consists of one master node and two slaves that replicate a database
from master (all run on CouchDb version 1.3.0). The web application gets the
response from either slave.
Is there a way to ensure that both CouchDb
View etags implicitly depend on update orderings that are not
guaranteed over replication.
Or to say that slightly differently, you would only have identical
view ETags if you could guarantee that you made the same exact updates
in the same exact order on both nodes (which is something that
I've confirmed that the native view server honors that timeout, can
you tell me what;
curl localhost:5984/_config/couchdb/os_process_timeout
returns? You might need to bounce couchdb in any case, as it applies
this timeout setting when it creates the process, and we keep a pool
of them around,
iirc native query server has hardcoded timeout 5000 and ignores
os_process_timeout setting.
--
,,,^..^,,,
On Wed, Dec 18, 2013 at 10:05 PM, Robert Newson rnew...@apache.org wrote:
I've confirmed that the native view server honors that timeout, can
you tell me what;
curl
couch_native_server has the set_timeout callback, though. I'll re-test shortly.
B.
On 18 December 2013 18:17, Alexander Shorin kxe...@gmail.com wrote:
iirc native query server has hardcoded timeout 5000 and ignores
os_process_timeout setting.
--
,,,^..^,,,
On Wed, Dec 18, 2013 at 10:05
Yes, reconfirmed my finding. I added ?LOG_INFO lines to the
set_timeout clause in couch_native_server and it gets the current
os_process_timeout value. That's a bit silly (given it's not an os
process) but at least it's configurable. I stand by my original reply.
B.
On 18 December 2013 18:31,
Great work, Travis! I'm eager to see more happen in CouchDB-land around
the use of JSON-Schema.
FWIW, I'm playing with some MapReduce for identifying content--when you
don't know what you're getting:
https://github.com/cloudant-labs/Spellbook/tree/master/content-identification
It's sort of
Dave,
Thanks for the extensive description. It’s a little hacky indeed but I’ve
learned quite a bit from your approach. We’re getting closer!
From a different perspective, what is the reason to not include Persona into
the regular build of CouchDB? Is it to prevent growth of the distribution?
On 18/12/13 18:05, Robert Newson wrote:
I've confirmed that the native view server honors that timeout, can
you tell me what;
curl localhost:5984/_config/couchdb/os_process_timeout
restart CouchDB on 1.2 (latest in Ubuntu) then
curl
There is something hard coded in there and I will find it eventually
and find why it was put there and by whom.
This attitude might discourage people from helping you with your efforts.
B.
On 18 December 2013 22:33, david martin david.mar...@lymegreen.co.uk wrote:
On 18/12/13 18:05, Robert
On Dec 18, 2013, at 2:08 PM, Sjoerd de Jong sjo...@weett.nl wrote:
From my point of view, Persona is great way to have decent security in a
really simple setup. It enables couchapps to be fully secure, without the
need of installing any other services, which is a major feature imho. As
Why did you place quotes around your timeout? Its just the value... No
quotes
On Dec 18, 2013 2:42 PM, Robert Newson rnew...@apache.org wrote:
There is something hard coded in there and I will find it eventually
and find why it was put there and by whom.
This attitude might
15 matches
Mail list logo
