Add initial Spree migration article #2640
Merged
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
swcraig
reviewed
Mar 20, 2018
|
|
||
| If you use Rails's default asset pipeline, for example, we recommend that you | ||
| explicitly update the versions of the `sass-rails` gem in your `Gemfile`, as | ||
| well as explicitly setting the versions for the dependencies `sprocket` and |
| ``` | ||
|
|
||
| At this point, the update should run successfully. If it does not, check your | ||
| `Gemfile` for other gems that require specific updated to their dependencies. |
There was a problem hiding this comment.
I think this should be "require specific updates".
| ### Manage depreciation warnings | ||
|
|
||
| After upgrading your Spree 2.4 application to Solidus 1.4, you may see some | ||
| deprecation warnings. The amount of depreciation warnings depends on how many |
There was a problem hiding this comment.
"The amount of deprecation warnings"
|
|
||
| After upgrading your Spree 2.4 application to Solidus 1.4, you may see some | ||
| deprecation warnings. The amount of depreciation warnings depends on how many | ||
| Spree features you use that are being depreciated in Solidus, as well as |
There was a problem hiding this comment.
I think "deprecated" instead of "depreciated".
| Spree features you use that are being depreciated in Solidus, as well as | ||
| additional gems your application uses. | ||
|
|
||
| If you plan to upgrade to Solidus 2.0, you need to deal with the depreciated |
There was a problem hiding this comment.
I think "deprecated" instead of "depreciated".
| break existing functionality in your application code. | ||
|
|
||
| Use the notes in [Solidus's changelog][changelog] to help you upgrade to each | ||
| minor version of Solidus gracefully. |
| ## Migrating from Spree 3.0 or newer | ||
|
|
||
| Solidus is a fork of Spree 2.4. After Spree 2.4, the Spree and Solidus code | ||
| bases start to diverge. For example, Spree 3.0 introduces is a Bootstrap-based |
There was a problem hiding this comment.
"Spree 3.0 introduces is a"
| frontend and backend which is significantly different than Solidus's frontend | ||
| and backend. | ||
|
|
||
| time and preparation than other migrations. If you run Spree 3.0 and want to |
There was a problem hiding this comment.
I think the start of this sentence got chopped somewhere.
benjaminwil
force-pushed
the
migration_documentation
branch
2 times, most recently
from
9733724
to
96a280d
Compare
This article walks the reader through a simple migrations from Spree Spree 2.4 to Solidus 1.4. Then, it encourages readers to incrementally upgrade to newer versions of Solidus. Both Spree 2.4 and Solidus 1.4 are pretty old now. It would be great to have an additional article that details a (more complicated) migration from Spree 3.x to Solidus 2.x. This would necessarily need to be simplified.
gmacdougall
approved these changes
Apr 17, 2018
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.
This article walks the reader through a simple migrations from SpreeSpree 2.4 to Solidus 1.4. Then, it encourages readers to incrementally upgrade to newer versions of Solidus.
Both Spree 2.4 and Solidus 1.4 are pretty old now. It would be great to have an additional article that details a (more complicated) migration from Spree 3.x to Solidus 2.x. This would necessarily need to be simplified.
This is part a larger project to improve Solidus's documentation. See this gist with the high-level table of contents. Where and how this documentation will exist is still up for discussion.