Don't we already have a db-per-user plugin/feature thing? Could
Fauxton just not make use of that? Beyond that I'd rather not go
creating more "special" databases as it's already leading to some
rather complicated interactions with all of the various "features" we
have to add to make each new type
I like the idea of a database per user. I thought about creating such a
database by Fauxton upon login, but that won't work if the user does not
have admin privileges, so I guess this is something that should be
implemented in Couch itself.
Unfortunately I can't make any contribution to this cod
Trimming the long thread for readability...
Good news, everyone! As of the latest checkin to master, CouchDB 2.0
builds correctly on Windows 64-bit! All eunit and javascript tests
pass (or are skipped intentionally).
This is a huge milestone! I especially want to thank Nick North and
Dave Cottle
We’ve tagged RC1, build here as usual:
http://couchdb.apache.org/release-candidate/2.0/
@Clemens, the git tag is `2.0.0-RC1` :)
Best
Jan
--
> On 15 Jul 2016, at 08:53, Jan Lehnardt wrote:
>
> In fact, now all commits to couchdb.git master will produce a tarball here,
> automatically: http
On Fri, Jul 15, 2016 at 3:19 PM, Constantin Teodorescu
wrote:
> Just wanted to know where are (in 2.0 release) the old files:
>
>- _utils/script/jquery.couch.js
>- _utils/script/base64.js
>- _utils/script/sha1.js
>- _utils/script/json2.js
>
> I'm using *jquery.couch.js* in a lot of
> On 15 Jul 2016, at 14:19, Constantin Teodorescu wrote:
>
> On Thu, Jul 14, 2016 at 11:55 PM, Jan Lehnardt wrote:
>
>> New tarball with the changes here:
>>
>>
>> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-2dddaf0.tar.gz
>>
>> untar, ./configure, make ./dev/run , ever
On Thu, Jul 14, 2016 at 11:55 PM, Jan Lehnardt wrote:
> New tarball with the changes here:
>
>
> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-2dddaf0.tar.gz
>
> untar, ./configure, make ./dev/run , everything is working OK on Ubuntu
15.10 and 16.04 64 bit
Just wanted to k
I was speaking to Jan about this in #couchdb-dev. He makes some very
important points:
+jan> thing is, fauxton runs under the security context of the logged
in user
11:12 J<+jan> so each user would need their own fauxton db
11:12 J<+jan> or we bleed info
11:12 J<+jan> or it is admi
Markus, good points. I'm definitely +1 for the idea. Like Samuel says,
storing notifications would be excellent. It would definitely allow us to
improve the user experience.
Cheers
Garren
On Fri, Jul 15, 2016 at 8:45 AM, Samuel Kidman wrote:
> It would be nice to store notifications in such a d
