This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of hoodie.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Before this change, we loaded admin accounts from CouchDB’s /_config/admins API or for PouchDB we simply set the password to "secret" and wrote it into .hoodie/config.json
We dropped persisting the admin password altogether and instead made it an option: adminPassword. If it’s not set, then no admin account exists.
CouchDB’s _users database is configurable at /_config/couch_httpd_auth/authentication_db. We read out this configuration and used it as the name of the users database. But as we don’t rely on the special behavior of CouchDB’s users database (auto-hashing of passwords) we can use any normal CouchDB database to store the accoutns of Hoodie. And as the /_config API is not implemented by CouchDB-like hosters like Cloudant, we want to store this configuration ourselves.
For now, we hardcode the database name to default to _users. The name can be configured via options.account.usersDb.
Hello lovely humans,
hoodie just published its new version 26.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of hoodie. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
26.0.0 (2017-01-05)
Bug Fixes
Features
adminPasswordoption (10e9c36b)Breaking Changes
Before this change, we loaded admin accounts from CouchDB’s
/_config/adminsAPI or for PouchDB we simply set the password to"secret"and wrote it into.hoodie/config.jsonWe dropped persisting the admin password altogether and instead made it an option:
adminPassword. If it’s not set, then no admin account exists.(5899eda1)
Before storing the secret in the database using PouchDB, it was stored in different ways based on the adapter.
/_config/couch_httpd_auth/secret<data path>/config.jsonTo migrate to this version, create a database
hoodie-configwith a document{"_id": "hoodie", "secret": "<your secret here>"}(cd055af1)
CouchDB’s
_usersdatabase is configurable at/_config/couch_httpd_auth/authentication_db. We read out this configuration and used it as the name of the users database. But as we don’t rely on the special behavior of CouchDB’s users database (auto-hashing of passwords) we can use any normal CouchDB database to store the accoutns of Hoodie. And as the/_configAPI is not implemented by CouchDB-like hosters like Cloudant, we want to store this configuration ourselves.For now, we hardcode the database name to default to
_users. The name can be configured viaoptions.account.usersDb.(e9ee7a06)
(142e9a7a)
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade