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.
Description
At present, if someone follows the local dev setup instructions verbatim, the docker-compose file that actually gets run upon
docker compose up
is the one at the top level of this repo (not either of the docker-compose files in packages/server); that docker-compose file sets environment variables from .env.test, in particular the db username and password. Then upon running the prisma migrate step, there will be db auth errors if the environment variables in that shell are not also set according to .env.test.I don't know what the intended steps are supposed to be (is the db actually supposed to be spun up from one of the other docker-compose files?) so this was just the quickest path to instructions that don't result in errors; just close this PR if not appropriate
Checklist