Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First-time setup and dev docker compose config overhaul #1620

Open
wants to merge 13 commits into
base: dev/10.3.0
Choose a base branch
from

Conversation

clpetersonucf
Copy link
Member

@clpetersonucf clpetersonucf commented Nov 13, 2024

The goal of this PR is to make the first-time setup process more robust while offering a setup variation for non-developers, to better facilitate an on-ramp for a production environment.

run_first script split

The previous docker/run_first.sh script has been split into two variations:

  • run_first_for_dev.sh, more or less in parity with the existing run_first.sh script
  • run_first_for_nondev.sh, which provides for a-la-carte configuration options to enable a leaner, faster setup.

Docker compose override changes

The default docker-compose.override.yml file is no longer included by default and is untracked. Dev-specific compose configurations that previously lived in docker-compose.yml now live in a new docker-compose.development.yml. The docker-compose.override.yml file is dynamically authored by either of the two run_first script variants during first-time setup.

Development env variable changes

The previous docker-compose.yml file included explicit references to a variety of environment variable configurations that made it difficult to override. These values have been reduced to dev-specific values that are themselves generated from the docker/.env file. The docker/.env file has been expanded with dev environment variables that can be overridden in docker/.env.local as desired.

nginx configuration changes

There is now a third nginx config: nginx-nondev.conf, which is used in non-dev setups. This configuration bridges the gap between pure dev nginx configs and the production nginx config to allow both previous options to remain unchanged.

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