Make couchdb database writable for any user but readable for just one user
up vote
0
down vote
favorite
I want to create a Couchdb 2.0 database such that
- just a single registered user can read documents in it (and this may be the database admin)
- any registered user can write to it.
Taking my clue from several other people I want to set up Couchdb such that any request to:
/{db}/{docid}
will be rewritten in such a way that it is handled by a _rewrite function in the design document in {db}. As I understand it, this implies that it should be rewritten to:
/{db}/_design/ddoc/_rewrite/{db}/{docid}
This design document will contain a function that (for a GET request) compares the user in the request object with the owner of the database (a constant in the function). Only when equal will the document be returned.
I modelled the rewritten url on my (rather feeble) understanding of the rewrite documentation.
Now, is this correct? Or will any request to /{db} be routed through the _rewrite function anyway? If not, how do I set this up?
url-rewriting couchdb writeonly
add a comment |
up vote
0
down vote
favorite
I want to create a Couchdb 2.0 database such that
- just a single registered user can read documents in it (and this may be the database admin)
- any registered user can write to it.
Taking my clue from several other people I want to set up Couchdb such that any request to:
/{db}/{docid}
will be rewritten in such a way that it is handled by a _rewrite function in the design document in {db}. As I understand it, this implies that it should be rewritten to:
/{db}/_design/ddoc/_rewrite/{db}/{docid}
This design document will contain a function that (for a GET request) compares the user in the request object with the owner of the database (a constant in the function). Only when equal will the document be returned.
I modelled the rewritten url on my (rather feeble) understanding of the rewrite documentation.
Now, is this correct? Or will any request to /{db} be routed through the _rewrite function anyway? If not, how do I set this up?
url-rewriting couchdb writeonly
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to create a Couchdb 2.0 database such that
- just a single registered user can read documents in it (and this may be the database admin)
- any registered user can write to it.
Taking my clue from several other people I want to set up Couchdb such that any request to:
/{db}/{docid}
will be rewritten in such a way that it is handled by a _rewrite function in the design document in {db}. As I understand it, this implies that it should be rewritten to:
/{db}/_design/ddoc/_rewrite/{db}/{docid}
This design document will contain a function that (for a GET request) compares the user in the request object with the owner of the database (a constant in the function). Only when equal will the document be returned.
I modelled the rewritten url on my (rather feeble) understanding of the rewrite documentation.
Now, is this correct? Or will any request to /{db} be routed through the _rewrite function anyway? If not, how do I set this up?
url-rewriting couchdb writeonly
I want to create a Couchdb 2.0 database such that
- just a single registered user can read documents in it (and this may be the database admin)
- any registered user can write to it.
Taking my clue from several other people I want to set up Couchdb such that any request to:
/{db}/{docid}
will be rewritten in such a way that it is handled by a _rewrite function in the design document in {db}. As I understand it, this implies that it should be rewritten to:
/{db}/_design/ddoc/_rewrite/{db}/{docid}
This design document will contain a function that (for a GET request) compares the user in the request object with the owner of the database (a constant in the function). Only when equal will the document be returned.
I modelled the rewritten url on my (rather feeble) understanding of the rewrite documentation.
Now, is this correct? Or will any request to /{db} be routed through the _rewrite function anyway? If not, how do I set this up?
url-rewriting couchdb writeonly
url-rewriting couchdb writeonly
asked Nov 19 at 16:04
Joop Ringelberg
227
227
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378513%2fmake-couchdb-database-writable-for-any-user-but-readable-for-just-one-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown