You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The diff is no longer current. It's unclear how this can be fixed and to fix existing indexes.
Also, code-level patch is very undesired for administrators - does the patch need to be there all the time or just when the index is created? I do not want to maintain a fork of the code with all the recent security issues - can't this be handled with code/config?
Mastodon instance
No response
Mastodon version
main-latest
Technical details
If this is happening on your own Mastodon server, please fill out those:
For what it's worth, here's the patch I came down from v4.2.12. Not a pro of ElasticSearch here, just copied everything from the current docs and it got my server (kind of) working.
Steps to reproduce the problem
Try to follow the setup here:
https://docs.joinmastodon.org/admin/elasticsearch/#search-optimization-for-other-languages
The current code does not match the diff.
Expected behaviour
Docs can be followed
Actual behaviour
Diff no longer valid
Detailed description
The diff is no longer current. It's unclear how this can be fixed and to fix existing indexes.
Also, code-level patch is very undesired for administrators - does the patch need to be there all the time or just when the index is created? I do not want to maintain a fork of the code with all the recent security issues - can't this be handled with code/config?
Mastodon instance
No response
Mastodon version
main-latest
Technical details
If this is happening on your own Mastodon server, please fill out those:
ruby --version
, eg. v3.1.2)node --version
, eg. v18.16.0)The text was updated successfully, but these errors were encountered: