Skip to content
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

Confusion in docs #62

Open
asennoussi opened this issue Jun 13, 2014 · 2 comments
Open

Confusion in docs #62

asennoussi opened this issue Jun 13, 2014 · 2 comments

Comments

@asennoussi
Copy link

Hello !
Where should I put the realm.properties file ? is it in etc/elasticsearch/config (folder doesn't exist natively ) or in jetty plugin config file ?
Also , does jetty secure the get and post methods as well ?
and finally , should we add the jetty lines in all cluster members ? or just the master ?
thanks

@pmusa
Copy link

pmusa commented Jun 18, 2014

I suggest you post on:
https://groups.google.com/forum/?hl=en#!forum/elasticsearch-jetty

About the confusion in the docs, the documentation is clear in my opinion:

realm.properties in the config directory of elasticsearch
So yes, it is the same folder of the elasticsearch.yml

Regards,
Pablo

2014-06-13 20:40 GMT-03:00 Sshuichi notifications@github.com:

Hello !
Where should I put the realm.properties file ? is it in
etc/elasticsearch/config (folder doesn't exist natively ) or in jetty
plugin config file ?
Also , does jetty secure the get and post methods as well ?
and finally , should we add the jetty lines in all cluster members ? or
just the master ?
thanks


Reply to this email directly or view it on GitHub
#62.

@dominicsayers
Copy link

Hi Pablo, I had the same problem so thanks for clearing this up.

In my opinion "the same folder as elasticsearch.yml" is much clearer than "in the config directory of elasticsearch".

I was looking for a directory called config in my ElasticSearch installation directory, and there wasn't one so I was confused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants