|
|
I'm using this to deploy Geeklog code using pear. This is still a work in progress but when combined with Pear Package for Geeklog :: Post Install Script it makes site deployment a breeze. I use this build script on pretty much all of my pear packages, all that needs to be changed is the ignore files and a few notes here and there.
I maintain a number of unique Geeklog installations and use pear packages to manage builds and maintain a repository. When a pear package gets deployed it moves the old version of a file, and replaces it with the new version, so you lose file permissions in the process. Some sites that undergo a lot of changes start to be a headache to maintain, especially if you're working with a server admin that has to update permissions for you. I put together this quick post-install script to handle that process for us. Now each package deployment can update it's file system and database after it's installed, with very little interaction from the developer and/or site admin. This whole process is being ironed out right now, and will hopefully help make PCI compliant safe_mode enabled web applications simple to maintain with pear.
I've posted the script I use, along with the Pear Package for Geeklog :: Build Package so you can see how I get a pear post-install script added to a build.
|
|
