Skip to main content

Managing multiple Plone buildouts

I recently had situation in work where I needed to update several of our Plone sites with few addon products. So far we haven't thought how we'll manage our sites update story as we've basically just recently entered to the amazing world of buildouts and several Plone-sites instead of one huge plone-site with zeo.

Gotta say I had few ideas popping in my head when I was manually running buildout scripts for each of our sites and stopping and restarting them after buildout was completed. My first though was to just simply write some script which does the job and then I was already imaging some web based service so we could manage our sites buildouts ttw. Well.. that might be a bit overkill.. at least for the starters, so I went back to roots and wrote a small python application which does the job. Basically it just takes the list of buildouts and runs buildout-script with -Nv parameters and restarts the site.

Source code is below and in the github.


from subprocess import check_call
from subprocess import CalledProcessError

#BUILDOUT_LIST is a list of folders where you're sites are
class Buildout:
"""Takes care of managing one buildout"""

def __init__(self, path):
self.path = path
self.dev_null = open('/dev/null','wb')

def instance_cmd(self, command):
if command == 'start':
print "Starting %s instance..." % self.path
elif command == 'stop':
print "Stopping %s instance..." % self.path

check_call(['./' + self.path + '/bin/instance', command],)

except CalledProcessError, e:
print e.returncode

def run_buildout(self):
print "Trying to run buildout for %s " % self.path
dev_null = open('/dev/null','wb')
check_call(['bin/buildout', '-Nv'],
stderr=dev_null, stdout=dev_null)
print "Buildout for %s completed succesfully" % self.path

except CalledProcessError, e:
print "Error while running buildout for %s: %s" % (self.path,

class BOManager:
""" Launches buildout scripts """

def __init__(self, buildouts):
self.buildouts = buildouts

def giveitago(self):
for buildout in self.buildouts:
print "-"*40
bo = Buildout(buildout)
print "-"*40+"\n"

if __name__ == '__main__':
buildout = BOManager(BUILDOUT_LIST)

Popular posts from this blog

Domain name registration through Google - when things go wrong.

Not too many people know, that you can register new domains through Google. This can be done when you're registering for Google Apps Standard Edition which is free and somewhat stripped version of their Google Apps Premium Edition. Latter one is tailored more to suit business needs.

With $10/year prize tag it's not cheapest option, but you'll get "private domain registration to protect against spam at no extra cost, full DNS control and domain management, automatically configured to work with Google services, email, calendar, instant messaging, web pages and more also at no extra charge".

As a comparsion GoDaddy offers .org domains at $14.99/year so it's actually not that bad offer. Google actually is just collecting the data and sending it to their partners (godaddy, enome) which does the registration. I decided to give it a try at January 11th. To my big surprise things didn't went that smoothly. It's been now one week since my order - the domain I …

Usability and Plone

I've seen in here and there someone mentioning that usability of Plone is very good. Lot's of people - me included - like the fact that in Plone you don't have separate content management interface compared to some of Plones rivals. That counts for something when we're talking about good usability. Still that is only one quite small part of the whole picture. So what else is there? What do people like in Plone and where are the rough edges for end users? If general consensus is that Plone does have good usability, where is the actual proof of that?

On I found one page in developer documentation mentioning following: "Plone differentiates itself on usability. The intuitiveness of the user interface is what attracts people to Plone the most."

I interpret this sentence meaning about the "one view for all" approach. What bugs me in this is that this whole sentence about good usability is about how the UI works compared to Plones competitors. S…

Whiskers - a tool for keeping track of your buildouts

Few years ago I released a first version of Whiskers together with buildout.sendpickedversions. It's about the time to push new version out.

What is Whiskers?
Whiskers is a Pyramid web application which stores information about your buildouts so that you don't have to manually check what they contain. All the data to Whiskers is transferred by buildout.sendpickedversions - an buildout extension which keeps track of packages your buildout uses and sends the data in json-format to Whiskers-server.

Reason for Whiskers?
Main reason for me to develop Whiskers was based on the need of knowing what packages I have in our servers. I'm working at the University of Jyväskylä and part of my job is to maintain our Plone instances. We have about 100 Plone instances with slightly varying setup. If we needed a new version of some specific package it meant lots of work to have a list of Plone-sites which needed the update. With Whiskers I know what to update after few clicks.

New tricks