Rails 3 migration attempt #2
Open
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
* Created Rails 3.0.7 bones * Got to the point the migrations are actually running ;) * Moved gem requirements to Gemfile * Removed all gems/plugins that are completely outdated and break the migrations
|
Maybe this is a dead project ... A shame really that their creators do not give continuity. :-( |
|
Hi - did the Rails 3 migration work in the end? |
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.
I noticed discussions in Google Group you created a Rails 3 branch and got challenged to see if we could migrate Lovd. Since, LovdByLess was my first Rails project I learned from several years ago (btw, thanks Steve for the support), I would like to contribute back and see how difficult it is going to be. Hopefully, we wont need to rewrite the entire app ;)