Fundraising tech/Deployment

Release tags and branches
Please note that many repositories include checked-in external libraries. This should only be done on the deployment branches, the master branch is rebuilt by the developer. Do check in composer.lock and similar files for version locking.

Configuration
Change paymentswiki configuration files on the frack puppetmaster, boron.

fr-tech doesn't have access to configure some subsystems directly.

Deployment process
Fundraising cluster deployment is always done from boron. Software is deployed using the custom fundraising_code_update and rsync_blaster scripts, configuration is deployed with boron as the puppetmaster. More information is available about deployment on Collab.

SmashPig
Deploying SmashPig as a composer dep of crm is very involved:


 * commit smashpig/master
 * update composer.lock sha1 in crm/master (would be great if we could composer update)
 * commit crm/master
 * check out crm/deployment
 * merge crm/master
 * composer install
 * commit crm/vendor/master
 * update submodule ref for vendor in crm/deployment
 * commit crm/deployment