♻️ Run bundle when migrations present #14
Closed
Conversation
This file contains 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
Prior to this commit, we might have a situation where the initialize_app container's gems are not what is indicated by the Gemfile.lock. Which creates problems when we run the `bundle exec rails db:create`; namely the error will mention that we don't have the gem installed. We can circumvent this via different docker compose files; however, it seems reasonable to demand that we `bundle` before we execute `bundle exec`; especially when we consider the fact that we're not always running migrations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prior to this commit, we might have a situation where the initialize_app
container's gems are not what is indicated by the Gemfile.lock. Which
creates problems when we run the
bundle exec rails db:create; namelythe error will mention that we don't have the gem installed.
We can circumvent this via different docker compose files; however, it
seems reasonable to demand that we
bundlebefore we executebundle exec; especially when we consider the fact that we're not alwaysrunning migrations.