Documentation bookmarks for self and others

Useful parts of the various documentation efforts now available within the Zope community:

• Zope components and interfaces
• Acquisition
• ZODB: the part from the ZDG and the ZODB wiki page
• Testing, Debugging & co: Testing and Debugging (ZDG), Testing in Plone, Python Profilers
• Buildout tutorial for Plone

Let’s get Plone 3 support for Plone4ArtistsVideo

I am starting an active support to Plone4ArtistsVideo because I like this product. More, I think Plone 3 and beyond needs it as an important add-on. It means we can all reuse its pieces in our projects.

Thanks to Nate Aune for starting this effort. I just pledged to help make that happen.

Then I am going to contribute, at least by testing and documenting (not sure if it was already done) how you can use it as part of your development (integrating, adaptation/subtyping and all).

Improving your Plone site’s performance

Plone experts know this. But the others need to know it too. After all, we’re all on the same boat !

You’re in the testing phase of your Plone project, and you find it slow ? Take the following corrective actions, and stop worrying !

• Use a ZEO-based setup. This is important ! You can distribute the load on 2 or more ZEO clients. (Note that the ZEO server and clients can all be on the same machine.)
  It is possible to bind a ZEO client to a special type of requests such as “content contribution requests”. This way, you keep the other ZEO client(s) responsive for the “normal” requests.
  If you need automatic load balancing, add a load-balancer software such as Pound in front of the ZEO clients.

• Take advantage of Zope’s HTTP Cache Managers.
  • A simple fix you can do for Plone 2’s default HTTP Cache Manager ; go on the HTTPCache object, and uncheck the “Cache anonymous connections only?” option. There is no reason you should not cache static content such as skin images/files for Authenticated users.
  • Invest a little more to go further with CacheFu-based caching policy management tools.
• Install a Squid proxy-cache. It is recommended to serve the site with Zope behind Squid (or Zope behind Squid behind Apache).
  There is also Varnish as an alternative to Squid, though I haven’t yet tested it.

Started using OpenID

In about 10 mn, I created my account @ claimID.com, and then tested by logging on twitterfeed.com and adding the feed of my blog for the twitter account I created a couple of days ago. We’ll see how it works !

Next thing to do : test it on a Plone 3.0 site (which has support for OpenID OOTB.) Yeah !