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

expose or not InfluxDB API #8

Open
cskiraly opened this issue Jun 6, 2017 · 2 comments
Open

expose or not InfluxDB API #8

cskiraly opened this issue Jun 6, 2017 · 2 comments

Comments

@cskiraly
Copy link
Contributor

cskiraly commented Jun 6, 2017

Apart from our own API, there is a question whether to expose the InfluxDB API.
There are clear advantages (e.g. using InfluxDB specific nodes) and disadvantages (e.g. exposing the implementation).

The proposal from @nopbyte was not to expose it by default, but leave it user configurable.

@craigmulligan
Copy link
Contributor

Yea I agree, atm it's configurable by adding an EXPOSE statement to the docker compose file.

@cskiraly
Copy link
Contributor Author

cskiraly commented Jun 7, 2017

OK, lets keep it like that till we figure our how to expose such config options towards a user.

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

2 participants