Skip to main content

Home/ Plone distributed documentation/ Group items tagged start

Rss Feed Group items tagged

Graham Perrin

When the Plone installer isn't enough - Immersive Training Experience - 0 views

  • ZopeSkel to get everything started
  • buildout that is based on the latest best practices
  • products and add-ons
  • ...9 more annotations...
  • 10 minute getting started
  • In this case, we want a Plone 3 buildout that grabs the latest stable version of Plone.
  • repeatable deployments
  • cd mysite
  • python bootstrap.py
  • buildout profiles that extend one another
  • paster create -t plone3_buildout mysite
  • predictable results
  • sure to get the same deployment every time you run bin\buildout
Graham Perrin

Saving the day: recovering lost objects - Jarn · Plone Solutions - 1 views

  • recovering lost objects
  • entire section of his site was missing
  • someone had deleted the object
  • ...26 more annotations...
  • 9 days earlier
  • Undo was no longer an option
  • Truncating the Data.fs (removing all transactions since, including the offending one)
  • undesirable
  • through RelStorage
  • time traveling: zc.beforestorage
  • small additional buildout configuration file
  • beforestorage.cfg
  • [buildout]extends = buildout.cfgeggs += zc.beforestorage ZODB3 zope.proxy[versions]ZODB3 = 3.8.1zope.proxy = 3.4.2[relstorage-patch]recipe = plone.recipe.commandcommand = cd ${buildout:eggs-directory}/ZODB3-3.8.1-py2.4-linux-i686.egg/ZODB curl -s http://svn.zope.de/zope.org/relstorage/tags/1.1c1/poll-invalidation-1-zodb-3-8-0.patch | patch -N -p0 cd ${buildout:directory}update-command = ${relstorage-patch:command}[instance]zope-conf-additional += enable-product-installation False
  • enable-product-installation
  • tells Zope not to try and write product information to the ZODB
  • because zc.beforestorage puts your ZODB in read-only mode
  • edit the zope.conf
  • <zodb_db main>    # Main database    cache-size 650000%import zc.beforestorage%import relstorage <before> before 2008-12-08T10:29:03    <relstorage>        <oracle>            dsn RELSTORAGE_DSN            password xxxxxxxxx            user xxxxxxxx        </oracle>    </relstorage> </before>    mount-point /</zodb_db>
  • impossible as the site stores
  • <before> before 2008-12-08T10:29:03    <relstorage>        <oracle>            dsn RELSTORAGE_DSN            password xxxxxxxxx            user xxxxxxxx        </oracle>    </relstorage> </before>
  • when you start the instance, you are in the past
  • found the lost object
  • Export/Import
  • save the export on the server
  • buildout with your regular buildout file
  • restart
  • import the .zexp
  • reindex the imported content
  • related data that lives outside of the object itself is gone
  • Martijn Pieters
Graham Perrin

Jon Stahl's Journal » Blog Archive » Plone 4: three times faster than Drupal,... - 0 views

  • Plone 4 is faster out of the box than some of the most common PHP platforms
  • three times faster than Drupal, Joomla and Wordpress
  • Plone 4
  • ...26 more annotations...
  • Jan 19th, 2010
  • Jon Stahl
  • Plone 4 is about to
  • enter beta testing prior to a final release
  • performance
  • out of the box
  • over three times faster
  • what does all this mean?  Well, honestly, not much
  • realistic sample content
  • very, very proud of Plone’s raw speed
  • suspect MAMP not to be very efficient
  • For read-only operations, once the objects have made it into ZODB’s object cache no database queries need be made
  • the difference is down to Plone’s use of the ZODB
  • Contrast this to the PHP/MySQL systems which must perform several selects in order to render the page
  • to fetch new objects it’s slower
  • ZODB fetches are serial
  • Archetypes persistent object design is far from optimal (page data is split over several persistent objects, slowing down load time)
  • addressed as part of Dexterity
  • fundamental architectural difference
  • CMSes that use the RDBMS and some kind of ORM or manual SQL (like Drupal, Joomla)
  • those that use an OODBMS such as Plone
  • ‘out of the box’ speed, since that is something a lot of people historically have not liked about Plone
  • less tuning needed to start with
  • even when caching is not applicable we still get the performance boost
  • our installer sets up ZEO with clients for you, so this is “out-of-the-box”
  • counter the (incorrect) perception out there that “Plone is slow”
Graham Perrin

On Plone documentation - Martin Aspeli - 1 views

  • I think it's a mistake to try and solve all the problems with "Plone documentation" in the same way
    • Graham Perrin
       
      +1
  • rely more on technology
  • What is current good practice?
    • Graham Perrin
       
      My initial reaction to this: get started | essential actions | refinements and current best practice …
  • ...20 more annotations...
  • a corpus small enough that it can be effectively reviewed
  • highlighted and easy to find
  • this is where they should be stumbling
    • Graham Perrin
       
      Can we elaborate on this point?
  • Barriers to entry should be low
  • version the document pertains to
    • Graham Perrin
       
      +1
    • Graham Perrin
       
      Re http://dev.plone.org/plone/ticket/7831 some simple triggers might draw attention to documentation that becomes outdated (or at least deserves review) at product update time.
  • concerned about how easy it is to add an article
  • highlight the "good" bits of documentation
  • reviewed at least each time we make a new Plone release
  • What's the right way to configure caching?
    • Graham Perrin
       
      Advice may be diverse.
  • If someone wants to contribute documentation, by all means let them!
  • allow comments
  • ratings of the type "was this helpful to you"
    • Graham Perrin
       
      I do often rate things (positively more often than negatively). However: I rarely observe other people's ratings.
  • Open the flood-gates
  • group documentation by audience, rather than by type
    • Graham Perrin
       
      I'm never wholly convinced about audience-based documentation.
    • Graham Perrin
       
      Can we group documentation by layer - through the Plone (TTP), Zope management interface (ZMI), file system et cetera?
  • Accept that how-to documentation won't be perfect
  • Add ratings
  • improve commenting
  • this is out of date
    • Graham Perrin
       
      Maybe "This is valid for version n.n of product x" plus "For more recent advice please visit …".
  • We should allow people to make requests for new documentation, and expose the wish list in a way that lets people vote for their favourite requests
    • Graham Perrin
       
      First improvements to a document might be: (1) a link to Trac, so that any documentation-related issue can be tracked; and (2) an in-document summary of relative tickets.
  • We have a Trac
Graham Perrin

Amberjack Lightning Talk - 0 views

1 - 6 of 6
Showing 20 items per page