Hi Joan,
Yes, I'm planning to maintain it, and hopefully it's readable enough for
others to do so if necessary. In any case, since current Cloudant Local
customers are being encouraged (with few on-prem alternatives) to migrate
to CouchDB, there should be a built-in user base for as well. This is
I remember this code!
Sure, let's get it out there, *as long as* someone is going to maintain
it going forward.
I had been hoping to see more rallying behind how to use the JWT
integration for OAuth and SAML workflows, but no one's done any
walkthroughs / blogposts that I've seen. Putting
Hi Joan,
Thanka for the effort in exploring these possibilities. Along with those,
we could have another choice:
https://github.blog/2020-09-01-introducing-github-container-registry/
Alessio
Il lun 31 ago 2020, 20:41 Joan Touzet ha scritto:
> On 31/08/2020 14:36, Joan Touzet wrote:
> > I'm
Same - keep for now, choose to deprecate later.
Remember by our semver policy this would mean the earliest this endpoint
could be removed would be CouchDB 5.0 (!)
-Joan "time keeps on slippin', slippin'..." Touzet
On 2020-09-01 4:35 p.m., Jonathan Hall wrote:
Thanks for the explanation.
I
Thanks for the explanation.
I concur, I prefer compatibility, but as I'm not coding it, I'll defer the
decision to others.
Jonathan
On Sep 1, 2020, 10:30 PM, at 10:30 PM, Paul Davis
wrote:
>Replication of deletions isn't affected due to the new_edits=false
>flag like you guessed. This is
Replication of deletions isn't affected due to the new_edits=false
flag like you guessed. This is purely "interactively creating a new
document that is deleted". Its a fairly minor edge case in that the
document must not exist. Any other attempt to "revive" a deleted doc
into a deleted state will
Isn't compatibility required to support replication of deleted documents? Or
does creation of a deleted document work with new_edits=false?
On Sep 1, 2020, 10:16 PM, at 10:16 PM, Nick Vatamaniuc
wrote:
>Hi everyone,
>
>While running PouchDB replication unit tests against the CouchDB 4
Hi everyone,
While running PouchDB replication unit tests against the CouchDB 4
replicator PR branch (thanks to Garren Smith, who helped set up the
tests), we had noticed a doc update API incompatibility between
CouchDB 3.x/PouchDB and the prototype/fdb-layer branch: CouchDB
3.x/PouchDB allow
Greetings,
In 2015 IBM Cloudant developed an LDAP based authentication handler for
its CouchDB 2.x-based Cloudant Local offering. Since then, it has been used
in production on several large Cloudant Local deployments, accruing many
bug fixes and enhancements in the process.
Over the years, there
Nice
--
Robert Samuel Newson
rnew...@apache.org
On Tue, 1 Sep 2020, at 16:24, Jan Lehnardt wrote:
> This PR by my coworker Jacoba should address this issue satisfactorily:
>
>https://github.com/apache/couchdb-fauxton/pull/1292
>
> Best
> Jan
> —
>
> > On 27. Aug 2020, at 11:41, Jan
This PR by my coworker Jacoba should address this issue satisfactorily:
https://github.com/apache/couchdb-fauxton/pull/1292
Best
Jan
—
> On 27. Aug 2020, at 11:41, Jan Lehnardt wrote:
>
> In ermouth's defence, I also think that the PR was merged prematurely. But
> adding a button with a
11 matches
Mail list logo
