feat: expose pouchApp from spawnServer #1992
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains:
Describe the problem you have without this PR
I am wanting to use rxdb with pouchdb-auth, to provide user authentication, but I am unable to define an admin user at first startup.
This is because pouchdb-auth requires them to be defined as part of its config, which is only exposed on the pouchApp object this exposes. If an admin user is not defined, then every client will be an admin, so not having this control makes securing the master database on first startup very hard.
An example of how the result of this can be used for this is:
There was some other fiddling I need to do with raw PouchDB databases to get the client side rxdb setup with pouchdb-auth, but that is fine. (I think just configuring pouchdb-auth with the special _users database)
Todos