I think you'll have to edit plume-models/src/config.rs so that Rocket knows the URL of this "plume" database.
6de9a1f1c8
Merge pull request 'Recreate search index if its format is outdated' (#802) from KitaitiMakoto/Plume:invalid-index into main
Honestly, it makes me wonder if actix wouldn't be more appropriate for our use case… we would get actors and a web framework out of the box. I think we already tried to migrate once and it didn't went very far, right? What was blocking?
But I'm okay with refactoring our code with Riker and keeping Rocket too.
010eac6c4a
Merge pull request 'upgrade rocket* to the latest stable' (#800) from igalic/Plume:update/rocket into main
@trinity-1686a I don't know if you set up Drone with Docker, but it looks like /tmp/cache is not available, could you create a directory and mount it in Docker at this path, please? Or do an equivalent operation if you are not using Docker.
What I can tell out of my head is:
- benefits:
- we can clearly see which routes use the database, and which don't
- we will probably have less custom code if we use the
#[database]attribute that generates some code for us, I guess.
- drawbacks:
- not sure it is the case, but maybe we won't be able to migrate to
sqlxwith the#[database]attribute, I don't know what types SQLx supports, and if they are compatible with Rocket's attribute.
- not sure it is the case, but maybe we won't be able to migrate to
- alternatives:
- keeping it the way it is? but that makes the async migration harder, so it is not really an option
Clippy shouldn't be unhappy either, it is just one parameter, so I'm all
6238bbd6c5
Merge pull request 'Update lindera-tantivy to v0.1.3' (#796) from KitaitiMakoto/Plume:update-lindera-tantivy into master