Website releases made easy with the PEAR installer, OSCON 2009

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Ask people what they use and how they use it

    Deploying websites with the PEAR installer is an alternative, not a replacement for other approaches.

    Tasks, custom file roles and so on are done with something we are familiar with ....

    Each piece of site has its own package.xml file The website it self has its own package.xml

    Security implications

    Good place to study how things are built up

    Now we run these pseudo packages and we want to install only part of our website structure This will install your only those 3 parts of your website along site all the deps which one of those is the Website .

    Favorites, Groups & Events

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

    1. OSCON, July 2009
    2. Head of R&D at echolibre , pear extraordinaire, published author, party person and an Icelander
    3. Not just for website deployment. Also for ... Application deployment
    4. Other solutions
      • FTP Upload
      • SCP / rsync
      • Capistrano
      • SVN / CVS / Git / <insert here>
      • etc etc etc
    5. Alternative, not a replacement.
    6. PEAR Installer features to the rescue File roles Tasks Post installation tasks Provides plugin architecture
    7. PEAR Installer features to the rescue upgrade. depend on external packages. split websites into plugin pieces. Easy to
    8. Last but not least...
    9.  
    10. 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 ;-)
    11. Dismantling your site Split your site into logical plugins Do not split into as many packages as you can! Micro management is bad, mmmmkay
    12. Web Services Backend Frontend Forum Website
    13. 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
    14. 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”
    15. File Roles Default file roles: php , test , data , doc , cfg , www , script , ext & src People have written their own custom file roles.
    16. Custom file roles In relation to templates Custom handling of data files Just to name few
    17. Post installation tasks PHP task that you run after the installation
    18. 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
    19. Need to know about post install We do not run post install script auto!
    20. pear run-scripts pear/pearweb Including external post-installation script &quot;/usr/share/PEAR/pearweb.php&quot; - any errors are in this script Inclusion succeeded running post-install script &quot;pearweb_postinstall->init()&quot; init succeeded Install database? [y] : pear run-scripts pear/pearweb Including external post-installation script &quot;/usr/share/PEAR/pearweb.php&quot; - any errors are in this script Inclusion succeeded running post-install script &quot;pearweb_postinstall->init()&quot; init succeeded Install database? [y] :
    21. Post install task Multiple questions that have multiple options Ability to skip question group based on user input
    22. 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:
    23. 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
    24. Puzzling the pieces together pear install –a Website_WebServices Website_Frontend Website_Backend
    25. Web Services Backend Frontend Website
    26. Questions?
    27. http://pear.php.net/manual/en/ http://www.packtpub.com/PEAR-Installer/book PHP Architect Articles [email_address] @h on twitter Resources

    + Helgi Þormar ÞorbjörnssonHelgi Þormar Þorbjörnsson, 4 months ago

    custom

    344 views, 0 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 344
      • 344 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 5
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories