github-starred/couchdb-best-practices
2
0
Fork 0
mirror of https://github.com/jo/couchdb-best-practices.git synced 2026-05-15 14:16:00 -06:00
Code Issues 232 Projects Releases Packages Wiki Activity Actions

[GH-ISSUE #77] Link failed #674

New issue
Closed
opened 2026-04-18 22:01:09 -06:00 by gitea-mirror · 5 comments
gitea-mirror commented 2026-04-18 22:01:09 -06:00
Owner
Copy link

Originally created by @fredguth on GitHub (Apr 18, 2022).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/77

The reference to "control access on a per document level " is no longer valid. Do you have a link for this content elsewhere?

Originally created by @fredguth on GitHub (Apr 18, 2022). Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/77 The reference to "[control access on a per document level](https://wiki.apache.org/couchdb/PerDocumentAuthorization) " is no longer valid. Do you have a link for this content elsewhere?
gitea-mirror commented 2026-04-18 22:01:11 -06:00
Author
Owner
Copy link

@jo commented on GitHub (Apr 18, 2022):

Hi @fredguth, thanks for pointing that out! The old wiki no longer exists and it looks like the content has not been migrated. Work is underway to implement per-document access: https://github.com/apache/couchdb/issues/1524

I have updated the document here.

<!-- gh-comment-id:1101379962 --> @jo commented on GitHub (Apr 18, 2022): Hi @fredguth, thanks for pointing that out! The old wiki no longer exists and it looks like the content has not been migrated. Work is underway to implement per-document access: https://github.com/apache/couchdb/issues/1524 I have updated the document here.
gitea-mirror commented 2026-04-18 22:01:12 -06:00
Author
Owner
Copy link

@fredguth commented on GitHub (Apr 18, 2022):

Sorry to once again contact you via issue. Is there a tiny project using a crypto box to solve per document authorization?
I understand all the concepts in theory, but I do not feel confident in applying them because I fear doing something really wrong. My goal is to offer services with the "translucent database" approach.

<!-- gh-comment-id:1101446582 --> @fredguth commented on GitHub (Apr 18, 2022): Sorry to once again contact you via issue. Is there a tiny project using a crypto box to solve per document authorization? I understand all the concepts in theory, but I do not feel confident in applying them because I fear doing something really wrong. My goal is to offer services with the "translucent database" approach.
gitea-mirror commented 2026-04-18 22:01:13 -06:00
Author
Owner
Copy link

@jo commented on GitHub (Apr 18, 2022):

Sadly there is none open sourced I'm aware of. Do you have the concept written somewhere so I can have a look?

<!-- gh-comment-id:1101462846 --> @jo commented on GitHub (Apr 18, 2022): Sadly there is none open sourced I'm aware of. Do you have the concept written somewhere so I can have a look?
gitea-mirror commented 2026-04-18 22:01:13 -06:00
Author
Owner
Copy link

@fredguth commented on GitHub (Apr 18, 2022):

I will do that and share with you. I am revisiting a project I developed in 2015-2016 that used pouch/couchdb with one-db-per-user (now defunct). Interestingly, it looks similar (visually) to Immmr, you worked on.

<!-- gh-comment-id:1101517125 --> @fredguth commented on GitHub (Apr 18, 2022): I will do that and share with you. I am revisiting a project I developed in 2015-2016 that used pouch/couchdb with one-db-per-user (now defunct). Interestingly, it looks similar (visually) to Immmr, you worked on.
gitea-mirror commented 2026-04-18 22:01:13 -06:00
Author
Owner
Copy link

@fredguth commented on GitHub (Apr 20, 2022):

I invited you to Couchello which is intended to be a Demo project for current CouchDB best practices.

<!-- gh-comment-id:1103323790 --> @fredguth commented on GitHub (Apr 20, 2022): I invited you to [Couchello](https://github.com/fredguth/Couchello) which is intended to be a Demo project for current CouchDB best practices.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
gh-pages
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/couchdb-best-practices#674
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?