-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update meilisearch #543
Comments
The Meilisearch upgrade procedure (when running in a container) is a massive pain in the arse (and I say this as someone who uses it daily). For a project like this upgrading it in-place is practically impossible. It is going to be far easier to have people re-create their Meilisearch index on the new version and re-index. Does the reindex all bookmarks button in the admin interface do this? |
That's exactly what it does yes. |
so clearing the meilisearch data, start with new version, and then reindex all bookmarks should work? |
Yeah bring the whole stack down, backup & delete the |
@wuast94 as long as newer version of mellisearch work with their old clients (they are keeping client backward compatibility), this should work yes. Reindexing is extremely fast. |
then i will try it the next days and report back :) |
There is already an issue #426 but without any usefull information.
my main reason is security. running old containers (v1.6 is 9month old and v1.9 what i use is 3month old).
running old containers is always a bad advice becouse they also have all the security issues of the base image, all old dependencys and app.
also recource usage, speed improvements etc are some things that are always nice to have.
The text was updated successfully, but these errors were encountered: