Advantages of recommended GIT repository setup with Umbraco cloud
Hi,
I was wondering about the advantages of the recommend setup (as detailed here in the Visual Studio Setup section) where we are advised to have two different repositories. 1. The web repository: the "deployment repository" (with the View folder) AND
2. The core repository - "source code repository" (with the Model and the Controller files).
If we use branches to develop features, would this not necessitate the creation of two branches, one in each repository, for the same feature?
For example, if a controller developer is working on a feature, they would need to create a "matching" feature branch in both repositories (in case their feature has a UI impact and they want to test it as they develop).
Would it not be better in this scenario to have all the code be in one repository, namely the "deployment repository" and just create branches for separate features that would be merged to master subsequent to testing?
The deployment repository will deploy everything to your web server, so you don't want sensitive code files or anything you wouldn't want to deploy in that repo.
We actually duplicate the deployment repository into our source repository so those files are checked in to both repositories so we 1) have a complete backup in a single repository, and 2) we can branch the code repository and work in that for bigger updates. We just need to be sure to only commit to the deployment repository after we merge to our code master, and make sure we don't overwrite things between repos.
Advantages of recommended GIT repository setup with Umbraco cloud
Hi,
I was wondering about the advantages of the recommend setup (as detailed here in the Visual Studio Setup section) where we are advised to have two different repositories. 1. The web repository: the "deployment repository" (with the View folder) AND
2. The core repository - "source code repository" (with the Model and the Controller files).
If we use branches to develop features, would this not necessitate the creation of two branches, one in each repository, for the same feature?
For example, if a controller developer is working on a feature, they would need to create a "matching" feature branch in both repositories (in case their feature has a UI impact and they want to test it as they develop).
Would it not be better in this scenario to have all the code be in one repository, namely the "deployment repository" and just create branches for separate features that would be merged to master subsequent to testing?
Hi,
We adapted this workflow : http://skrift.io/articles/archive/integrating-umbraco-cloud-with-team-development-workflow/
We only used different tools to hanlde the deployment.
Dave
The deployment repository will deploy everything to your web server, so you don't want sensitive code files or anything you wouldn't want to deploy in that repo.
We actually duplicate the deployment repository into our source repository so those files are checked in to both repositories so we 1) have a complete backup in a single repository, and 2) we can branch the code repository and work in that for bigger updates. We just need to be sure to only commit to the deployment repository after we merge to our code master, and make sure we don't overwrite things between repos.
is working on a reply...