Clarify deployment options in Elasticsearch basics quickstart #1489
+4
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charlotte-hoblik
added
documentation
leemthompo
reviewed
May 28, 2025
leemthompo
approved these changes
May 30, 2025
There was a problem hiding this comment.
Suggested a slight reordering to lead with the escape hatch for users who already have a cluster, then provide a link to all deployment types and finally lead into the "OK OK I just want to spin up the fastest local cluster possible right now without reading any more docs" option :-)
leemthompo
reviewed
Jun 2, 2025
Co-authored-by: Liam Thompson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Made the quickstart intro clearer to show that that it works with any Elasticsearch deployment, not just local Docker.
Based on: https://github.com/elastic/developer-docs-team/issues/292