Google Git
Sign in
apache / couchdb-peruser / 39ef15a28e5be1d697c7c29dd64fcc18c24e7881
commit39ef15a28e5be1d697c7c29dd64fcc18c24e7881[log] [tgz]
authorILYA Khlopotov <iilyak@ca.ibm.com>Tue Aug 23 14:59:54 2016 -0700
committerILYA Khlopotov <iilyak@ca.ibm.com>Tue Aug 23 14:59:54 2016 -0700
tree9ed524213dc5f7b9988749ba52b091ca517285ac
parentff7d190970a46722137fbc7a1a75466e8a544ae1 [diff]
parented3ad6fc97e10bdae73e87b36f8c2446d5bf2fcf [diff]
Merge remote branch 'cloudant:3102-fix-config_subscription'

This closes #1

Signed-off-by: ILYA Khlopotov <iilyak@ca.ibm.com>
tree: 9ed524213dc5f7b9988749ba52b091ca517285ac
  1. src/
  2. test/
  3. .gitignore
  4. .travis.yml
  5. LICENSE
  6. README.md
README.md

couch_peruser Build Status

couch_peruser is a CouchDB daemon that ensures that a private per-user database exists for each document in _users. These databases are writable only by the corresponding user. Databases are in the form:

userdb-{hex encoded username}

For example, the user bob will have a database named userdb-626f62.

The reason for hex encoding is that CouchDB usernames have no restrictions, but CouchDB databases have restrictions. Hex encoding the UTF-8 representation of the username is a transformation that's easy to correctly implement in just about any language, especially JavaScript and Erlang. Other encodings would be possible, but would require additional client and server-side code to support that encoding. This is the simplest scheme that is obviously correct.