Add paperclip back to the gemfile so legacy migrations work. #1754
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.
I had a new contributor complain that running
rails db:migrate
didn't work and that our migrations were broken.It turns out that since we used to have paperclip in the application and we had a migration that depended on it we need to put this back to let new folks be able to run the migrations.
This is obviously a short term fix. We'll need to eventually remove the gem and the fix the migrations but this immediately unbreaks things and lets new contributors run migrations as expected.