docs(compose): point bare 'docker compose up' at ./start.sh on first run#53
Merged
Conversation
On a fresh checkout, a bare `docker compose up` fails with a cryptic `env file .../neo4j-auth.env not found` because that file is generated by the documented first-run bootstrap `./start.sh`. Compose can't rewrite that error text without regressing the env_file-based credential security or breaking bare `docker compose up` on subsequent runs, so this ties the exact error to its remedy where a confused user looks: a header comment in docker-compose.yml and a troubleshooting note in the README. No behavior/security change; the two retained docker tests still pass. 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
On a fresh checkout, a bare
docker compose upfails with a crypticenv file .../neo4j-auth.env not foundbecause that file is generated by the documented first-run bootstrap./start.sh. Compose can't rewrite that error text without regressing the env_file-based credential security or breaking baredocker compose upon subsequent runs, so this ties the exact error to its remedy where a confused user looks: a header comment in docker-compose.yml and a troubleshooting note in the README.No behavior/security change; the two retained docker tests still pass.