chore(external docs): Document dependencies#4547
Conversation
Signed-off-by: binarylogic <bjohnson@binarylogic.com>
There was a problem hiding this comment.
👍 I like this structured content, but it isn't immediately clear to me when something should be "dependency" vs. "setup" vs. a "how it works" section. For example, there seems to be some overlap between what might have been a "dependency" section in the docker source and the "setup" section.
Or the apache section could have equally been written as a "setup" section with steps like:
- Make sure apache is running
- Edit the httpd.conf file and add the mod_status line
- Reload apache
- Verify that you can curl the endpoint
Maybe we should just have "setup" and drop "dependency"?
| `DOCKER_VERIFY_TLS` are set (as well as other Docker environment variables). | ||
| See the [Docker daemon docs][urls.docker_daemon_socket_option]. | ||
| If you'd prefer not to collect Docker logs through the Docker | ||
| API Vector offers alternative strategies. In some sets |
There was a problem hiding this comment.
| API Vector offers alternative strategies. In some sets | |
| API Vector offers alternative strategies. |
|
Yeah, this is very much in flux. I pushed it up to get your opinion on the My goal is to remove as much of the writing as possible since it'll be difficult to ensure quality and consistency across a team of developers. |
Signed-off-by: binarylogic <bjohnson@binarylogic.com>
Signed-off-by: binarylogic <bjohnson@binarylogic.com>
Signed-off-by: binarylogic <bjohnson@binarylogic.com>
Signed-off-by: binarylogic <bjohnson@binarylogic.com>
Signed-off-by: Brian Menges <brian.menges@anaplan.com>
Signed-off-by: binarylogic bjohnson@binarylogic.com