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.

Sign up for GitHub

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

Jump to bottom

[new page] [all products] Administration - Production config #165

Closed
beckettsean opened this issue Jan 20, 2016 · 3 comments
Closed

[new page] [all products] Administration - Production config #165

beckettsean opened this issue Jan 20, 2016 · 3 comments
Labels
Needs dev Time commitment: project

Comments

@beckettsean
Copy link
Contributor

Our products are all currently configured for the developer use case, with security disabled, everything talking over localhost, etc.

We should have a page for each product that describes the config and architecture choices we recommend users evaluate when moving from dev to production.
@beckettsean
Copy link
Contributor Author

Page should also mention client libraries, telegraf, kapacitor, etc. in appropriate context for best production architecture. Basically "don't roll your own, use tools in the ecosystem"

@beckettsean
Copy link
Contributor Author

Need to mention influxdata/influxdb#6444

@beckettsean beckettsean mentioned this issue Apr 22, 2016
Closed
@beckettsean beckettsean modified the milestone: 1.0 Jun 2, 2016
@stevebang
Copy link
Contributor

Closing -- while a good idea, best use of doc team time is adding production guidelines for 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs dev Time commitment: project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@beckettsean @rkuchan @stevebang