Discussion Forum

philp

Member

Registered: April 5, 2012

Posts: 25

Development workflow

I'm curious to know if you guys have any advice on a good way for a small development team to work with BigTree. I'm thinking mainly about how to keep local database instances synced, or whether it's better to have a single, remote development DB.

Also, slightly related to this: is it fairly easy to upgrade a BigTree installation for a project once it's in development?

benplum

Administrator

Registered: March 30, 2012

Posts: 54

Re: Development workflow

If you're using something like MAMP to develop locally, one way to keep databases in sync is to use daily SQL backups. Apps like Sequel Pro make the import/export process really simple. Internally, we use a dedicated development server, so we all work from one file system.

Upgrading BigTree should be as simple as replacing the core folder. Our goal is to keep backwards compatibility between minor versions; Major version upgrades may require some development time. Any big changes that do require development time will be outlined in that version's release notes. We're currently releasing new beta versions about once a week - when a new version is released, simply upload the new core folder and refresh your admin. If you're using GIT, simply pull the latest from the "Development" branch.