4 ms·
We have build scripts for phing, exports from subversion, migrates the database, loads stored procs, triggers and views, creates symlinks for data here and ther
by atstsolutions 16y ago
We have build scripts for phing, exports from subversion, migrates the database, loads stored procs, triggers and views, creates symlinks for data here and there, creates our dojo build layers, and builds a couple of executables we need.
Capistrano is better for the simple stuff, but once we started doing more we moved to phing.
- dclaysmith 16y agoWe have a bash script which grabs the latest Phing config/property files and then Phing handles the rest... * calls YUI Compressor to minify css/js * calls a custom script to upload images to the CDN * calls dbdeploy to update our staging database * symlinks the "built" revision to our staging site When we push a build from staging to production, we run a small bash script that calls Phing which symlinks the desired revision to the production site.
- albahk 16y ago+1 Phing. We use Phing for deploying to production and deploying a staging instance of the app. Phing can checkout from SVN, run a mysqldump to snapshot the DB, modify text files (i.e. different .htaccess files for staging/production), run arbitrary shell commands and ping web-APIs for notification etc. Deploys take between 10 and 30 seconds.