Version 1.8.0a1 (testing release)

This is an alpha release and should be considered unstable. Your local database should not be touched but you should still make a backup. Use at your own risk. If you already had external database support set up, make a backup of your external database, too.

This testing release brings back the external database functionality. MySQL has been briefly tested. PostgreSQL has not been tested. Please report any problems related to database support to the bug tracker or comment +1 on issues that have already been reported if you are affected, too. For questions that are not bugs, you can also open a ticket or visit the Octoprint Discord. Please use the channel #support-plugins.

If you do not need external database support, it is not recommended to install this update.

The release is mostly targeted towards people who already had external databases setup before the maintainer change. Consider the following hints if you want to setup external database support for the first time:

Please note that external database support requires manual installation of database and cryptography support, for example cryptography and pymsql from pip. This alpha version does not handle the installation of these packages.

To activate the external database, enter your connection data in the settings, test the connection and when you see a message that a table is missing, restart Octoprint. The database will then be initialized. Proper initialization without an Octoprint restart will be implemented later.

You can export your local SQLite database and import it to the external database after the external database has been initialized.

If you had already received this update, please open a ticket in the bug tracker and describe how you retrieved the update the first time and this time. It seems like the previous 1.8.0alpha was not correctly rolled out. This version now also includes all changes included in the stable release 1.7.6.

For the full list of changes, see the git commit list.