v0.9.1

Fixes

• add element-logo.png
• updated important keys in config.py to reflect new property names

v0.9.0

Features

• now uses alembic to up- or downgrade the database scheme

Please run the following after every update to make sure your database scheme is uptodate

alembic upgrade head

• #55 instead of one time token you can now set arbitrary amounts of usage per token via

 -m, --maximum INTEGER     times token can be used

• #38 new option in the config file to log IPs to the database
  these are viewable by checking the status of individual token via the cli or web api

Fixes

• #58 by renaming shared_secret to registration_shared_secret and
  admin_secret to admin_api_shared_secret

Changes

• addresses #16 by changing the web api:
  • every endpoint is now under the /api/ subdirectory
  • added a version endpoint /api/version that respons with e.g. {"version":"0.9.0.dev0"}
  • PUT -> PATCH for /api/token
• renaming the following properties
  • valid -> active
  • one_time -> max_usage
  • ex_date -> expiration_date

v0.9.0.dev0

Features

• now uses alembic to up- or downgrade the database scheme

Please run the following after every update to make sure your database scheme is uptodate

alembic upgrade head

• #55 instead of one time token you can now set arbitrary amounts of usage per token via

 -m, --maximum INTEGER     times token can be used

Fixes

• #58 by renaming shared_secret to registration_shared_secret and
  admin_secret to admin_api_shared_secret
• #38 by giving an option in the config file to log IPs to the database
  these are viewable by checking the status of individual token via the cli or web api

Changes

• addresses #16 by changing the web api:
  • every endpoint is now under the /api/ subdirectory
  • added a version endpoint /api/version that respons with e.g. {"version":"0.9.0.dev0"}
  • PUT -> PATCH for /api/token
• renaming the following properties
  • valid -> active
  • one_time -> max_usage
  • ex_date -> expiration_date

v0.8.0

Features

• the registration page is now available in english and german
• to help make matrix-registration available in more languages go over to:
  => https://l10n.dmnd.sh/engage/matrix-registration/

Fixes

• base_url should now also apply to css, see #47

v0.7.2

Features

• get automatically published docker builds here:

  • https://github.com/ZerataX/matrix-registration/packages/
  • https://hub.docker.com/r/zeratax/matrix-registration/tags

• new config option base_url which allows to set prefixes for the final url,
  e.g. use base_url: 'element/' for example.tld/element/register/

Fixes

• #44 issue where docker builds could not connect to a postgres db

v0.7.2.dev1

This is mostly a test release

Features

• publishes docker build to
  • https://github.com/ZerataX?tab=packages&repo_name=matrix-registration
  • https://hub.docker.com/r/zeratax/matrix-registration/tags
• new config option base_url which allows to set prefixes for the final url,
  e.g. use base_url: 'element/' for example.tld/element/register/

Fixes

• hopefully addresses #44

v0.7.1

Fixes

• #40, now uses the correct api endpoint thanks to #39 #41
• Waitress has a vulnerability below v1.4.2, see CVE-2019-16789

Notice

the new endpoint might not be exposed by some setups. make sure /_synapse is reachable on your homeserver.

v0.7.0

Features

• #35 dockerfile image size reduced to <100Mb
• #34 install a testing enviroment via pip with pip install -e .[testing]

Changes

• #34 cli app renamed: matrix_registration => matrix-registration
• #33 introduces a new config option admin_secret to choose a secret for the api
  previously this just reused the matrix homeserver's shared_secret, so if your api
  is publicly reachable please change this value

v0.6.1

Features

• #35 dockerfile image size reduced to <100Mb
• #34 install a testing enviroment via pip with pip install -e .[testing]

Changes

• #34 cli app renamed: matrix_registration => matrix-registration

v0.6.0

Features

• now uses SQLAlchemy and therefore supports postgres and other database schemes
• added docker image
• added nix shell support
• use waitress to serve application as a proper production wsgi server

Changes

• commands have slightly changed
  • gen => generate
  • api => serve

Troubleshooting

SQLAlchemy complains that a value isn't in a DateTime value

Before #17 introduced SQLAlchemy support the sqlite database incorrectly stored the expire dates, to fix this you have to manually run:

update tokens set ex_date=null where ex_date='None';

on your database once, or just delete your current database.