Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Updating corebos with commited fixes to master branch
#2
I would recommend you wait for official releases for most things. I plan to release about every other month (so it should be very soon now).
That way I will give specific steps to upgrade.

That said, git makes it really easy to follow development. The basic idea is:

- (optionaly) you fork the project
- you clone the repository git clone ..
- you install your production application which is now versioned
- when you want new update simply execute "git pull", that will bring in all the new code
- usually those code changes are associated to database changes, these should be reflected in the upgrade2corebos.php script, the problem is that we add changes there as we advance but only separate them from official release to release so you will have to weed through them to make sure you don't apply ones that are already in place.

On our roadmap is a project to make this MUCH easier, we are developing a database versioning scheme (copying liquibase philosophy) so that the code and the database are always in sync transparently, but it will be a while still...


Keep asking.
Joe
TSolucio
Reply


Messages In This Thread
Re: Updating corebos with commited fixes to master branch - joebordes - 06-09-2014, 09:02 AM

Forum Jump:


Users browsing this thread: 3 Guest(s)