-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make frontend/backend fully optional when installing spree gem #11105
Conversation
ee502ce
to
44797ed
Compare
189ad99
to
eb3b025
Compare
fa74675
to
99080ab
Compare
caf3401
to
73dfa97
Compare
ea38852
to
933460e
Compare
## Install missing migrations | ||
|
||
```bash | ||
rails spree:install:migrations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could add the frontend install command to the docs
bundle exec rails g spree:frontend:install
I've just fired this up locally
Notes: Had to use local path to the gems, as I think the frontend and backend stand alone gems are not published, or if published possibly need updating when the time is right. Documentation of the install commands is about the only thing I had to find out by a little digging during the install process: Other than that, very nice! |
Awesome! Yes, we need to update the docs after the first public 4.3 release and yes frontend/backend gems need to be updated on rubygems, actually you can run the generators/installers from the main one by: rails g spree:install --install_storefront=true --install_admin=true |
This makes Spree a more modular and headless API-first platform.
spree
gem does not includespree_frontend
norspree_backend
spree_frontend
andspree_backend
don't require specificspree_core
/spree_api
version, so older frontend can work with newerspree_core
(scenario: developer updated spree core, spree API but does not update spree frontend at the same time)