Skip to content

Conversation

jdkaplan
Copy link

@jdkaplan jdkaplan commented Jul 30, 2025

While trying to set up a local dev environment, I ran into a few issues with the Docker Compose setup and env file.

But these changes were all I needed to get set up. The rest of the process worked great!

This PR is split into individual commits (but I wouldn't mind squashing them):

  • Use an env template file to avoid committing test secrets

I almost committed my (test) credentials with a hasty git commit -a!

  • Add POSTGRES_PASSWORD to docker-compose.yml for local setup

This is the dev environment fix PR that @robbielyman mentioned in #190.

  • Wait to start dev containers until dependencies are ready

I found that this started the web container with fully-applied migrations a bit more reliably with less noisy error output.

  • Dedent docker-compose.yml

Entirely formatting. No offense taken if you drop this one!


  • Test
  • Screenshot
  • CHANGES.md entry
  • Documentation

Also, since this is my first interaction here, I want to say thanks for making and maintaining the Blaggregator! It's given me a lot of great stuff to read 😄

jdkaplan added 4 commits July 29, 2025 21:47
During my local dev setup, I noticed that the `web-variables.env` file
is gitignore'd, but Git keeps reporting it as a changed file. To avoid
accidentally committing those changes, I moved the example content to a
`web-variables.env.template` file (which will stay committable) and
updated the development instructions to match.
Newer versions of the `postgres` image (roughly January 2020 onwards)
require setting the POSTGRES_PASSWORD environment variable to be set.

This changes `docker-compose.yml` to use the formerly-default password
that the `web` container expects.
The current `depends_on` directives in `docker-compose.yml` are only
waiting until the dependency containers start, which causes first-time
setup to fail with a bunch of errors. This changes those directives to
instead wait until the database service is ready for queries and that
the migration step has completed sucessfully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant