Joan, thanks for the pointer to the documentation.
Sorry for being annoying, I have one more question. The doc states the
following:
"Note: This was designed without the guarantee that a DB event will be
persisted or ever occur in the _db_updates feed. It probably will, but it isn't
guarant
I'll update the docs. However, for now we have:
---
When a database is created, deleted, or updated, a corresponding event will be
persisted to disk (Note: This was designed without the guarantee that a DB
event will be persisted or ever occur in the _db_updates feed. It probably
will, but it i
Thanks Joan.
Very good to know. It'd be great to have this reflected somewhere in the
official couchdb 2.0 docs. Probably it is already there I just could not find
that...
thanks,
--Vovan
> On Jun 26, 2017, at 10:42 PM, Joan Touzet wrote:
>
> _db_updates is powered by the _global_changes da
_db_updates is powered by the _global_changes database.
-Joan
- Original Message -
From: "Vladimir Kuznetsov"
To: user@couchdb.apache.org, "Joan Touzet"
Sent: Tuesday, 27 June, 2017 12:39:55 AM
Subject: Re: _global_changes purpose
Hi Joan
I heard /_db_updates is the feed-like thing I
Sorry, it's been many years since I configured stunnel for use with
CouchDB, and I no longer have access to those configurations. I
remember it wasn't that complex from reading the stunnel docs.
My feeling is: the simpler the solution, the better. There is
simply less to go wrong with a tool that
Hi Joan
Can you please provide a little bit more details about 'nginx not correctly
reverse proxying chunked/multipart/etags/etc'? Can you also please provide
stunnel configuration file example.
Btw I've taken idea of using nginx at apache
wiki(https://cwiki.apache.org/confluence/display/COUCH
Hi Joan
I heard /_db_updates is the feed-like thing I could subscribe to listen to the
global updates(same way you described). It is not very clear why would I need
access to _global_changes database when I already have /_db_updates method with
pagination and long-polling features.
Is listenin
Say you have 100 databases and you want to know when something changes on all
of them. In 1.x you have to open 100 _changes continuous feeds to get that
information. In 2.x you have to open a single connection to _global_changes.
Think of the possibilities.
-Joan
- Original Message -
Fro
I'd recommend stunnel instead of nginx. We used to use it at Cloudant
and it worked fine. Gets you away from any worries about nginx not
correctly reverse proxying chunked/multipart/etags/etc correctly.
-Joan
- Original Message -
From: "Vladimir Kuznetsov"
To: user@couchdb.apache.org
Sen
Hi guys
I cannot find any good explanation what's the purpose of _global_changes system
database in CouchDB 2.0. Can somebody please explain or provide some pointer?
thanks
--Vovan
Hi guys
I'm planning to run CouchDB 2.0 cluster in EC2, probably 4 or 8 instances.
I want clients to use SSL certificate to authenticate so I want to run Nginx on
every CouchDB instance which will do SSL termination and forward connection to
the backend CouchDB instance running plain HTTP. Th
Hi Carlos,
Here's the reply (to the question I originally asked) I've got on parallel Dev
mailing list. Probably this helps answering your question:
The answer is slightly different depending if you're using 1.x/2.0 releases
or current master.
If you're using 1.x or 2.0 release: Set "max_replic
12 matches
Mail list logo