ElasticSearch Component for Docker Cluster #46
Merged
Conversation
This file contains 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
|
According to the last update of the ElasticSearch image for Alpine Linux |
|
@Grinnz I'm wondering if there is any issue with this development? |
|
Thank you and sorry I haven't looked at this. Hopefully will be upgrading to use elasticsearch 7 to 8 soon but this is great for now. |
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.
This development introduces the ElasticSearch Component as required in the Task #26 .
The "entrypoint.sh" Script already provides the logic to prepare the Web Application to connect to the ElasticSearch Cluster. So, the changes are few.
Still for complete integration on the development system additional actions are required by the System Administrator.
I also extended the Docker Deployment Documentation to include all needed information to set up the Docker Cluster correctly.
Following the guide at Perldoc Browser Docker Deployment any new contributor should be able to set up a working development environment in 30 min.
Closes #26