On Mon, Mar 15, 2010 at 3:47 AM, Mike <mikehorn1@gmail.com> wrote:
Quite a few of us work with spree in "vendored" mode - ie have it in vendor/spree
My personal preference is to use git submodules to embed spree in a project. Other people like to use symlinks to a separate spree clone. See http://spreecommerce.com/documentation/developer_tips.html#managinglargeprojects for more info.
I used to work via a master branch in my own fork, but it became quite a headache to keep in sync! Try the "spree-tweaks" extension technique if your changes are quite small.
Paul
-- I'm not sure what makes the most sense in terms of how we run Spree
going forward. I want to maintain the control over my app that I have
by not running it as a gem. But I'm assuming it's easier to get
patches and small updates to the stable branch when running in gem
mode. What's the best practice for developers who are actively
working with the code?
Quite a few of us work with spree in "vendored" mode - ie have it in vendor/spree
My personal preference is to use git submodules to embed spree in a project. Other people like to use symlinks to a separate spree clone. See http://spreecommerce.com/documentation/developer_tips.html#managinglargeprojects for more info.
I used to work via a master branch in my own fork, but it became quite a headache to keep in sync! Try the "spree-tweaks" extension technique if your changes are quite small.
Paul
You received this message because you are subscribed to the Google Groups "Spree" group.
To post to this group, send email to spree-user@googlegroups.com.
To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
No comments:
Post a Comment