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

Docs: How far we want to take it? #59

Open
svx opened this issue Mar 28, 2017 · 1 comment
Open

Docs: How far we want to take it? #59

svx opened this issue Mar 28, 2017 · 1 comment

Comments

@svx
Copy link
Member

svx commented Mar 28, 2017

This is now more my personal opinion, but I would like feedback, before I start writing stuff.

Here it comes:

I do not want to dive too deep into various topics, because often it is depending on your infra, personal taste and so on.

For example topics like, restarting, booting and so on ...

IMHO we should add to the beginning of the docs some short lines like:

If you going to use docker in production, we assume that you know what you are doing, bla bla

I am +1 for giving some examples for how you run a test container for playing, but for more serious stuff people should know what they are doing.

If you use rancher, swarm, dc/os, kubernetes, this is on you and not topic of the docs.

@demarant
Copy link
Member

I agree. We should not describe in details on how to deploy with specific clustering tools like rancher, swarm, dc/os, kubernetes. We should just explain the basic docker commands. For advanced clustering, if we know that some good examples exists, I would be in favor of "just" add some good stable references.

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

No branches or pull requests

3 participants