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

feat(docker): Add mix deps.get to Dockerfile CMD #2186

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

joshlarson
Copy link
Contributor

Summary of changes

Without this change, if a dependency is updated, then you have to fully rebuild the dotcom docker images. This change allows you to simply restart the containers, which will then pick up updated dependencies.

Depends on:

Note:

  • Having mix deps.get and mix deps.compile in the Dockerfile as well is still helpful because having the dependencies cached in the image allows mix deps.get to run much more quickly, and won't need to rebuild the dependencies when restarting a container.

General checks

  • Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
  • Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
  • Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

New UI, or substantial UI changes

  • Cross-browser compatibility is less of an issue now that we're no longer supporting IE, but changes still need to work as expected in Safari, Chrome, and Firefox.
  • Are interactive elements accessible? This includes at minimum having relevant keyboard interactions and visible focus, but can also include verification with screen reader testing.
  • Other accessibility checks such as sufficient color constrast, or whether the layout holds up at 200% zoom level.

New endpoints, or non-trivial changes to current endpoints

  • Have we load-tested any new pages or internal API endpoints that will receive significant traffic? See load testing docs
  • If this change involves routes, does it work correctly with pertinent "unusual" routes such as the combined Green Line, Silver Line, Foxboro commuter rail, and single-direction bus routes like the 170?

@joshlarson joshlarson requested a review from a team as a code owner October 4, 2024 17:11
@joshlarson joshlarson requested review from thecristen and removed request for a team October 4, 2024 17:12
Copy link
Collaborator

@thecristen thecristen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Base automatically changed from jdl/unify-dev-dockerfiles to main October 4, 2024 21:00
@joshlarson joshlarson force-pushed the jdl/mix-deps-get-in-cmd branch from 507f13b to e5b7ef1 Compare October 4, 2024 21:00
@joshlarson joshlarson enabled auto-merge (squash) October 4, 2024 21:00
@joshlarson joshlarson merged commit 9aa9425 into main Oct 4, 2024
17 checks passed
@joshlarson joshlarson deleted the jdl/mix-deps-get-in-cmd branch October 4, 2024 21:06
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.

2 participants