• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Oops, where's my site?
 

Oops, where's my site?

on

  • 845 views

How to install Plone add-ons and live to tell the tale

How to install Plone add-ons and live to tell the tale

Statistics

Views

Total Views
845
Views on SlideShare
826
Embed Views
19

Actions

Likes
0
Downloads
3
Comments
0

3 Embeds 19

http://coderwall.com 17
http://a0.twimg.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Oops, where's my site? Oops, where's my site? Presentation Transcript

    • Oops, wheres my site?How to install Plone add-onsand live to tell the tale
    • Goals • Know the procedure for installing most Plone add-ons • Understand guidelines to prevent things from breaking • Recognize some common ways installation fails and know how to recover
    • Starting on the same page
    • The flavors of Plone installers(Available from plone.org)Windows installer Only option for Windows.OS X For Mac OS X. Doesnt require a C compiler.Unified installer Installation from source for all Unix-like systems (including OS X). Requires a C compiler to install.Your own custom buildout Most likely generated using ZopeSkel or based on a previous project. Provides the most flexibility.
    • buildout rootThe directory that contains the rest of the installation.Windows C:Plone41Unified installer /usr/local/Plone/zinstance or $HOME/zinstanceCustom buildout Wherever you put it
    • instance scriptScript used to start Plone:bin/instance fgWindows C:Plone41bininstance fgOS X & Unified installer ${ ${buildout_root}/bin/instance fg } or ${ ${buildout_root}/bin/client1 fg }
    • First, do no harm
    • multi-staged deployment • Keep at least one copy of the site separate from the production copy, to test changes. • Keep all changes in version control (svn, git, etc.) so you can reproduce your environment. • Use buildouts extends to handle differences between environments.
    • Aspelis rule of deploymentCode & configuration flow from the development site to the production site; dataflows from the production site to the development site.
    • Back up your data before you make changes! 1. Make sure your buildout configuration is under version control. 2. Back up the data: $ bin/snapshotbackup -- or -- $ bin/backup(collective.recipe.backup is included in the Unified installer buildout.)
    • Restoring from backup1. Stop the instance2. Use your version control system to revert to the old version of the buildout, and re-run it.3. Restore the data: $ bin/snapshotrestore -- or -- $ bin/restore4. Start the instance.
    • The simplest backupCopy the entire buildout.
    • Preparing to install
    • Finding add-ons • Python Package Index (PyPI): http://pypi.python.org/pypi • Plone.org products directory: http://plone.org/products • Plone Open Comparison: http://plone.opencomparison.org
    • Plone version compatibility
    • DependenciesSimplest way to tell what it depends on is actually installing. :(Use the buildout.dumppickedversions extension:[buildout]extensions = buildout.dumppickedversions(Included in the Unified installer buildout.)
    • What does it do? • Does it do some trivial customization, or introduce a brand new experimental subsystem? • Does it do anything malicious? • Is it possible to uninstall?Ask others about their experience with it (on IRC or the mailing lists).
    • A simple installation
    • Buildout.cfg formatParts Each part has a header in square brackets: [buildout]Variables Each part contains multiple variables below the header: [buildout] extends = http://dist.plone.org/release/4.1.2/versions.cfg parts = instance Variables can interpolate other variables [instance] eggs = ${buildout:eggs}
    • Adding PloneFormGenAdd the name of the distribution to the eggs variable.Which part?[instance]eggs = Plone Products.PloneFormGenBut in the Unified installer buildout the instance eggs are based on thebuildout eggs:[instance]eggs = ${buildout:eggs}So you can add to buildout eggs:[buildout]eggs = Plone Products.PloneFormGen
    • Run buildout$ bin/buildoutFor verbose info:$ bin/buildout -vConfirm it was installedExamine the instance script.
    • Identifying picked versionsIf we used buildout.dumppickedversions, it shows us which versions were"picked":*************** PICKED VERSIONS ****************[versions]Products.PloneFormGen = 1.7b5Products.PythonField = 1.1.3Products.TALESField = 1.1.3Products.TemplateFields = 1.2.5#Required by:#Products.PloneFormGen 1.7b5collective.js.jqueryui = 1.8.5.2
    • Pinning picked versionsAdd them to the versions buildout part:[versions]Products.PloneFormGen = 1.7b5Products.PythonField = 1.1.3Products.TALESField = 1.1.3Products.TemplateFields = 1.2.5#Required by:#Products.PloneFormGen 1.7b5collective.js.jqueryui = 1.8.5.2Now if you re-run buildout, it should show no picked versions.
    • Inferior pinningWhy not do this?[buildout]eggs = Products.PloneFormGen==1.7b5Because the version doesnt get used if PloneFormGen is a dependency ofsomething else.
    • Being strict about pinningDisallow picked versions:[buildout]allow-picked-versions = false
    • Starting ZopeUse the instance script in foreground mode to make failures obvious:$ bin/instance fg
    • Activating the add-onSite Setup > Add-ons
    • A complex installation
    • Installing Dexterity[buildout]extends = http://good-py.appspot.com/release/dexterity/1.0.3?plone=4.1.2[instance]eggs = plone.app.dexterity
    • good-py • A tool for building and distributing known good sets • One KGS can extend another • A KGS can be constrained by a particular platform
    • Upgrading an add-on1. Update the version pins for the add-on and any dependencies.2. Re-run buildout and restart Zope.3. Go to Add-ons control panel and check if there are upgrade steps to run.
    • What could possibly go wrong?
    • Incompatible version pinsExample:The version, 1.1.2, is not consistent with the requirement,plone.app.jquerytools>=1.2dev.While: Installing instance.Error: Bad version 1.1.2Reason: PloneFormGen requires plone.app.jquerytools >= 1.2dev, but I have itpinned to 1.1.2.How did I know?:Getting required collective.js.jqueryui required by Products.PloneFormGen 1.7b6.Picked: collective.js.jqueryui = 1.8.13.1The version, 1.1.2, is not consistent with the requirement,plone.app.jquerytools>=1.2dev.While: Installing instance.Error: Bad version 1.1.2Solution: Upgrade plone.app.jquerytools (with care).
    • PyPI times outSymptom: Error message about the egg not being available.Solution: Temporarily use a mirror of the package index:[buildout]index = http://d.pypi.python.org/simple
    • ZCML not loadedSymptom: The product you installed doesnt show up in the Add-ons controlpanel.Reason: Many add-ons "announce" themselves to Plone so that Plone loads theirconfiguration, but some are missing this.Solution: Include the packages ZCML in buildout, re-run buildout, and restart:[instance]zcml = my.package
    • Other errors while starting upSeeking help: • Send the full traceback to the add-ons author • Ask in #plone channel on IRC • Ask on the plone-users mailing list
    • Room for improvement
    • plonelint tool
    • "Dry run mode" for buildout
    • Communal Known Good Set (KGS)
    • UI for installing packages
    • Questions