pouchdb

For a JavaScript web app (AngularJS based) I am using PouchDB replicating a CouchDB database on my server. Authentication in PouchDB works nicely with pouchdb-authentication . I want to manage this through a html/js login screen. However, if the user enters wrong credentials, I receive a 401 Unauthorized from the CouchDB server that causes a browser popup asking for credentials. How can I prevent this ugly Authentication popup and just handle everything from my javascript?! I finally found the solution: Edit the CouchDB config local.ini and change the HTTP Header sent in response: WWW

I come from a Mysql background and I'm using Pouchdb now. I'm used to the SQL pattern of having 1 database and many tables per app. In pouchDB it's different, because data is not stored in tables but in documents. So, in my app, I have a database for tasks, created with: var db = new PouchDB('tasks', {revs_limit: 1, auto_compaction: true}); This is the main database for my application, but now I need to also store settings, such as "last_visit_date", "language_preference" and others. So, I have 2 questions: Should I create only one database and then store different data sets in sub objects or

I am currently trying to write a CouchApp based on AngularJS 2. The data should obviously get stored in a CouchDB. The web app should get the data out of the DB using PouchDB. For authentication I thought about using Superlogin. Unfortunately I cannot figure out how to use PouchDB within ng2 and employ Superlogin for authentication. Furthermore, I am not even sure if it is possible to do all that without having a node.js server. Any help/advice will be appreciated. Thank you. Kévin I've just created the stack you mentioned. Is working perfectly, I'm really impressed. First I've followed this

I use the PouchDB-authentication plugin and I love it. However, I'm a little confused about the signup process and maybe I don't use it the right way. I use it to create new users in my CouchDB database but I don't understand why it is associated with a specific database? Since I create CouchDB user before his specific database, I have to use a dummy database to create the new user: // Create or get a database on the CouchDB server to further create a new user var remoteDB = new PouchDB('http://169.254.197.198:5984/dummy'); // Signup to this db in order to create new user in the CouchDB server

I wish to use PouchDB - CouchDB for saving user data for my web application, but cannot find a way to control the access per user basis. My DB would simply consists of documents using user id as the key. I know there are some solutions: One database per user - however it requires to monitor whenever a new user wants to save data in order to create a new DB, and may create a lot of DBs; Proxy between client and CouchDB - however I don't want PouchDB to sync changes for the whole DB including documents of other users in those _all_docs, _revs_diff request. Is there any suggestion for user access

I'm using pouchDB as a local database for an app. I want to query the results from PouchDB and load this into React.js. However, even though I'm using the waitFor() method the results of PouchDB query return too late. I think I don't understand the use of waitFor() correct, maybe someone can shed a light on it. I have two stores, the DbStore that retrieves data from the datbase. And the FileExplorerStore this store is used by my react components. DbStore.dispatchToken = AppDispatcher.register(function (payload) { var action = payload.action; var folder = payload.action.folder switch (action

What's the best security practice to follow while using PouchDB on the client-side to access a remote server? The example on https://pouchdb.com/getting-started.html syncs with the remote server with the code: var remoteCouch = 'http://user:pass@mname.example.com/todos'; The problem is I probably don't want the user to see the plaintext password with a file they can download -- even if that file is shown to the authenticated users only. Please advise. Thanks in advance, RamblinRose Here's a really good article regarding all things auth for CouchDB. I've got a production server with CouchDB