Full Version: Updating corebos with commited fixes to master branch
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I have seen a certain amount of fixes have been commited to the master branch of Corebos. I would like to know what procedure I should follow to apply those fixes to my installation witout needing to download the whole application again. Of course, I am refering on how to do this through github since that's what you advice me to do.

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.
Thanks. Will rather wait for the new version. Seems a bit complicated for me! <!-- sWink --><img src="{SMILIES_PATH}/icon_e_wink.gif" alt="Wink" title="Wink" /><!-- sWink -->
I understand <!-- s:-) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->

In any case it really is a good idea to have your code versioned. I really recommend this approach to everybody in the minimum case it is a good backup.
What do you mean by "code versioned" ?
using git or subversion to control the state of your code and all the changes that happen to it during it's production life span
it makes upgrading and controlling change a lot easier, also permits you to distribute easily a modified version you may create