Hi all,
I’m thinking about setting up a GIT system here for our development work.
The idea behind it is that I could set-up a repository called “Base Install” to clone each time I open a new project.
But I have a few questions…
Say I have 10 sites cloned from ‘Base’, and one day an extension used on all my sites is updated. Am I correct in thinking I can install this once onto ‘Base’, and then push that change out across all of the other sites?
In the above instance, the database may have changed to include new tables for that plugin. How would I sync the local database and live database up?
In a similar vein, if a customer wants to add a new feature to their site, I would make this on the GIT repo. Say I was adding “Membrr” to the website, and so I had some new tables, files and templates needing to be deployed. Naturally, I’d feel safer configuring the module on the local server and database before pushing it to the Live server - but I wouldn’t want to lose all of the changes they have made (new members, entries etc.) on the live server since I made the local copy of that database.
In short - the whole idea is exciting, but I can’t quite figure out how databases fits in to this workflow.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.