-
Notifications
You must be signed in to change notification settings - Fork 268
Tutorial: MeiliSearch in production #343
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
Tutorial: MeiliSearch in production #343
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a really great tutorial! I've learned so much reading through it. Thanks a lot. This is high quality stuff 🙌
|
Why did you chose to add the whole rust-toolchain installation instead of the binary download with curl? |
|
I remember while reading this tutorial that we have to write somewhere in the documentation that for best performance, it is always good to compile MeiliSearch on the machine you intend to run it because that way you will be sure that the binary will have all the optimization that the compiler could make for this specific architecture. Great content anyway @eskombro |
Thanks! The last version had the installation with the source code and compiling MeiliSearch. But after discussing a bit with @Kerollmops and @bidoubiwa it really seems that it adds some complexity and makes it too long for a 'tutorial' scope. Do you think we should reconsider it or add some side-note, or anything @tpayet ? |
|
Nope, I agree it may be useless in this scope. I just created the issue about writing the upper comment in the documentation (#346) |
DigitalOcean has strict guidelines about their name being written without spacing. Pretty sure I caught the last outlier!
Co-authored-by: mboivin <41596925+matboivin@users.noreply.github.com>
Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>
This is the Tutorial for running a MeiliSearch in production. Still needs to be checked by myself for grammar etc, checked by someone else for content validation / test, and finally go through some native English speaker for polishing purposes :)