Subscribe to my developers newsletter!

Hi Jeff, thanks for the newsletter :-)

What you can introduce next time could be how do you deploy on the cloud. As we have some customers on the cloud, everytime we are doinng some tricky things to deploy, such as exporting the studio to get the metadata files, git diff the whole isntance and get only the delta with the last tag, build manually with sugarcli the packages, etc ... 

We are curious to know how other partners are doing their deployments. (cc Christopher Cacciatore & Damien Pochon)

Hi Jeff, thanks for the newsletter :-)

What you can introduce next time could be how do you deploy on the cloud. As we have some customers on the cloud, everytime we are doinng some tricky things to deploy, such as exporting the studio to get the metadata files, git diff the whole isntance and get only the delta with the last tag, build manually with sugarcli the packages, etc ... 

We are curious to know how other partners are doing their deployments. (cc Christopher Cacciatore & Damien Pochon)

I like this one, I don't work in Cloud so a summary of how to do that would be nice.
Also, maybe, basic file structure and how to set up version control on your local copy, files to ignore, and how that plays into preparing the files for deployment.

Enes Saridogan: Here is my trick

Obtain the backup from Sugar Cloud from the ops_Backups module. 

Setup on your local computer

We utilize Source Code Control, git

git init
git add --all
git commit -m 'Files as provided by Sugar Cloud'

We also have a .gitignore, so we don't worry about things like the orderMappings*.php files changing.

Then you can make any/all changes that you would like and git will tell you what has changed.

Once we have the list of files, we have a package builder that will create a module loadable package.  The package builder requires some manual edits to the manifest so that custom fields, etc are loaded properly.