cherry-pick: Improves monitoring Neo4j standalone container docs (#175) #181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improves monitoring Neo4j standalone container docs
minor edits
Update modules/ROOT/pages/addition/docker/container.adoc
Update modules/ROOT/pages/addition/docker/container.adoc
Apply suggestions from code review
correct the doc formmating
formatted shell commands
combined 3 shell blocks into one with callouts
fix agent env config scripts
Apply suggestions from code review
Update modules/ROOT/pages/addition/docker/container.adoc
Apply suggestions from code review
If you open a PR that needs to go into a current version, you need to cherry-pick your commit from dev over to the current version branch. Only then will the proper builds that generate html/pdf be run. But beware: Docs will be generated but not published automatically!