github gabehf/Koito v0.1.8

6 hours ago

Highlights

SQLite support!

Before migrating, be sure to create an export of your data to ensure you do not lose any listening history! However, migration is a read-only process for your PostgreSQL database, so no data loss should occur (but I won't guarantee it for liability's sake). To migrate automatically, simply add KOITO_SQLITE_ENABLED=true to your environment variables. When Koito sees both that and KOITO_DATABASE_URL populated, it will automatically create a koito.db in your configuration root that will have all of your listening data, and Koito will immediately start using the new SQLite database.

Migration to SQLite will happen automatically on v0.2.0, so it is highly recommended to migrate manually beforehand to make sure everything goes smoothly!

Note that if Koito restarts and sees both environment variables populated, it will attempt another migration and fail to start, so after migrating you should remove KOITO_DATABASE_URL once you verify all your listening history is intact.

KOITO_ALLOWED_HOSTS is dead!

Remove it from your configuration. You don't need it, and it's value is now ignored and all hosts are allowed. I added this in the case Koito got more complicated, and I wanted to avoid a gethomepage-type situation where it gets added later on and causes issues with existing deployments. However, I've decided its too much trouble than it's worth, and I don't think Koito will grow enough in complexity to warrant it as an important security measure. This will also mean that, once SQLite is enabled by default in v0.2.0, Koito will be able to start with one container and absolutely zero configuration needed. A big win for simplicity!

Edit artists in the UI

Thank you to @onespaceman for the update that allows for adding and removing artists from tracks and albums in the UI.

What's Changed

New Contributors

Full Changelog: v0.1.7...v0.1.8

Don't miss a new Koito release

NewReleases is sending notifications on new releases.