Website releases made easy with the PEAR installer, OSCON 2009

OSCON, July 2009

Head of R&D at echolibre , pear extraordinaire, published author, party person and an Icelander

Not just for website deployment. Also for ... Application deployment

Other solutions
FTP Upload
SCP / rsync
Capistrano
SVN / CVS / Git / <insert here>
etc etc etc

Alternative, not a replacement.

PEAR Installer features to the rescue File roles Tasks Post installation tasks Provides plugin architecture

PEAR Installer features to the rescue upgrade. depend on external packages. split websites into plugin pieces. Easy to

Last but not least...

What is required The PEAR Installer Knowledge how to package your code with PEAR A bit of know how and RTM skills And not being afraid to read the source ;-)

Dismantling your site Split your site into logical plugins Do not split into as many packages as you can! Micro management is bad, mmmmkay

Web Services Backend Frontend Forum Website

The packages we get Website Website_Frontend Website_WebServices Website_Backend Website_Forum

Something to take note of
www role files install directly into web dir

Maintain only one website on the server Make every website have their own pear config Utilize the baseinstalldir attribute on the top dir
Ways to get past that “shortcoming”

File Roles Default file roles: php , test , data , doc , cfg , www , script , ext & src People have written their own custom file roles.

Custom file roles In relation to templates Custom handling of data files Just to name few

Post installation tasks PHP task that you run after the installation

Post installation tasks Post installation tasks Clean up after the installation, temp dirs or similar DB setup / upgrade tool Virtual Host adding / updating Prime Caches And just about anything you can dream up

Need to know about post install We do not run post install script auto!

pear run-scripts pear/pearweb Including external post-installation script "/usr/share/PEAR/pearweb.php" - any errors are in this script Inclusion succeeded running post-install script "pearweb_postinstall->init()" init succeeded Install database? [y] : pear run-scripts pear/pearweb Including external post-installation script "/usr/share/PEAR/pearweb.php" - any errors are in this script Inclusion succeeded running post-install script "pearweb_postinstall->init()" init succeeded Install database? [y] :

Post install task Multiple questions that have multiple options Ability to skip question group based on user input

Update pearweb database? [y] : 1. Database driver : mysqli 2. Database User name : pear 3. Database password : pear 4. Database host : localhost 5. Database name : pear 1-5, 'all', 'abort', or Enter to continue: Update pearweb database? [y] : 1. Database driver : mysqli 2. Database User name : pear 3. Database password : pear 4. Database host : localhost 5. Database name : pear 1-5, 'all', 'abort', or Enter to continue:

Real world example http://svn.php.net/pear/pearweb/package.xml http://svn.php.net/pear/pearweb/package-pepr.xml http://svn.php.net/pear/pearweb/pearweb.php In package.xml look for pearweb.php and you see how we do it for pear.php.net

Puzzling the pieces together pear install –a Website_WebServices Website_Frontend Website_Backend

Web Services Backend Frontend Website

Questions?

http://pear.php.net/manual/en/ http://www.packtpub.com/PEAR-Installer/book PHP Architect Articles [email_address] @h on twitter Resources

Website releases made easy with the PEAR installer, OSCON 2009

by Helgi Þormar Þorbjörnsson on Jul 30, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 3

Statistics

Website releases made easy with the PEAR installer, OSCON 2009 — Presentation Transcript