v26.0.0

<a name"26.0.0">

26.0.0 (2017-01-05)

Bug Fixes

• package: @hoodie/server@^22.0.0 (142e9a7a)

Features

• adminPassword option (10e9c36b)

Breaking Changes

• 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.

  (5899eda1)

• Before storing the secret in the database using PouchDB, it was stored in different ways based on the adapter.

  1. If the used PouchDB adapter was http (CouchDB), the secret was loaded from /_config/couch_httpd_auth/secret
  2. If the used PouchDB adapter was any other PouchDB adapter, the secret was stored in a file at <data path>/config.json

  To migrate to this version, create a database hoodie-config with a document {"_id": "hoodie", "secret": "<your secret here>"}

  (cd055af1)

• 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.

  (e9ee7a06)

  (142e9a7a)