-
Notifications
You must be signed in to change notification settings - Fork 75
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
Allow to activate ElasticSearch in a quick install environment #1234
Comments
bschmalhofer
added a commit
that referenced
this issue
Sep 15, 2021
bschmalhofer
added a commit
that referenced
this issue
Sep 15, 2021
bschmalhofer
added a commit
that referenced
this issue
Sep 15, 2021
bschmalhofer
added a commit
that referenced
this issue
Sep 16, 2021
into not replacing 'foreach' by 'for'.
Created https://github.com/RotherOSS/CodePolicy/issues/71 because CodePolicy was naugthy. PR is merged. Closing this issue. |
Reopening because it looks like the SysConfig changes for ElasticSearch were not deployed. |
bschmalhofer
added a commit
that referenced
this issue
Sep 21, 2021
that are activating Elasticsearch.
bschmalhofer
added a commit
that referenced
this issue
Sep 21, 2021
Issue #1234: actually deploy the changed setttings
The deployment has been added. Confirmed via the GUI that the deployment was successful. Closing again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bad effect wasn't recognised before, because the unit tests run without ElasticSearch support per default. It should be made easy to set up an environment with ES. Therefore I propose to add a flag
--activate-elasticsearch
to bin\docker\quick_setup.pl. Then test whether there are failures when running with ES.Originally posted by @bschmalhofer in #1192 (comment)
The text was updated successfully, but these errors were encountered: