search

vivo-community / vivo-vagrant

Vagrant configuration for VIVO
35 stars 30 forks source link

Good way to include a development mode in Vagrant? #9

Closed aviggio closed 10 years ago

aviggio commented 10 years ago

Would like to have ready access to separate Vagrant guest machines running different releases of VIVO. I'm starting to explore VIVO 1.7 RC2 and using the develop branch instead of the latest RC tag seems like one approach. Does this project support that as-is, or would there be a best solution to support this?

I started by cloning vivo-vagrant.git into a new directory, e.g. vivo-vagrant-1.7. Then I edited the provision/vivo/install.sh file as follows (lines starting with '<' indicate my revisions):

37c35
< #XXX: git checkout 1.6

---
> git checkout 1.6
41c39
< git checkout develop

---
> git checkout maint-rel-1.6
43c41
< git checkout develop

---
> git checkout maint-rel-1.6

Is there a better way to accomplish this, e.g. should the vivo-vagrant project's master branch follow the VIVO repo's develop branch, and instruct Vagrant users to do a git checkout v1.6 to build the "current release", as is done with older releases (currently just v1.5 as is documented in the readme)?

lawlesst commented 10 years ago

Editing provision/vivo/install.sh, like you describe, to checkout the branch or tag you want from VIVO's Git repository seems to be the most straightforward way to accomplish what you like.

There also can be changes to the build.properties or runtime.properties from version to version so it would be up to the user to make those changes in their Vagrant install. The same is true for other changes like the RDB migration that is part of the 1.6 to 1.7 upgrade.

lawlesst commented 10 years ago

Closing this because I think what you describe is what can be supported at the moment.