Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Add step to reset Gemfile.lock to TROUBLESHOOTING.md #445

Merged
merged 1 commit into from

4 participants

Kevin Ansfield discoursebot Régis Hanol Robin Ward
Kevin Ansfield

If bundle install is run after running bundle update then it will pull down the upgraded gems again. To avoid the issue it's necessary to reset Gemfile.lock to it's original state.

discoursebot

You've signed the CLA, kevinansfield. Thank you! This pull request is ready for review.

Régis Hanol
Owner

:+1:

Robin Ward eviltrout merged commit 98d314d into from
Robin Ward
Owner

Thanks for the clarification! :fish:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 1 deletion.
  1. +2 −1  docs/TROUBLESHOOTING.md
3  docs/TROUBLESHOOTING.md
View
@@ -25,7 +25,8 @@ reaching out to the community for help:
Don't. Running `bundle update` will download gem versions that we haven't tested with.
The Gemfile.lock has the gem versions that Discourse currently uses, so `bundle install`
- will work. If you ran update, then you should uninstall the gems and run `bundle install`.
+ will work. If you ran update, then you should uninstall the gems, run
+ `git checkout -- Gemfile.lock` and then run `bundle install`.
5. Have you migrated your database?
Something went wrong with that request. Please try again.