Posts Tagged ‘buildout’
David tries Plone 4.0a2 (Part 1)
Plone 4 is approaching! Excellent! Lots of new features to play around with and plenty more things to have to fix with the upgrade. I’ve been keeping tabs on the change log of updates and it’s looking really good. Lots of little, but significant, changes are afoot. Now, how about actually installing the Alpha 2 version of Plone 4 to see it for real? Let’s do it! (more…)
The biggest problems have the simplest answers…
..and how true that is. Today’s time consumer is directly related to just 1 misplaced line of a buildout configuration (and presumably something that’s changed somewhere else).
The result
After much hunting and hunting, it turns out my Zope2 Fake Eggs weren’t being generated. (more…)
Buildout: Best Thing Ever?
Taking a little bit of a time-out, I just have to ask the question: is Buildout not the best thing ever? (and the people who are so very kind to make the recipes?)
It’s made my work of managing our Plone infrastructure about 1000 times simpler since moving from Instancemanager (ughhh) and having to manually manage everything. I remember being a bit sceptical and very confused the first time I saw a buildout configuration file and thought that I’d never understand the thing.
Far, far from it of course! Whilst a little daunting at first, buildout has (in some/all metaphorical senses) won my heart. It couldn’t be easier to use, contrary to my initial (dis)beliefs.
Today sees me convert our archaic design of manually managing our Varnish RPMs and setup and changing it to buildout instead. Looks like the geniuses (and there’s no sarcasm here!) have made it perfectly – it does exactly what I need it to and makes my job so much simpler.
Buildout: Trying to create a Plone/Zope instance
Eeek…what’s this mean?
install() got an unexpected keyword argument ‘allow_hosts’
after trying to build zope2zeoserver from my buildout configuration. (more…)
Buildout: Trying to build Pound
So, trying to build pound through a Buildout recipe was failing part of the way through.
Two problems and their solutions (not necessarily in that order):
- Needed to install libssl-dev because lcrypto was missing (ambiguity anyone?) – Synaptic says that the package provides “libssl and libcrypto development libraries, header files and manpages” (but never mind a search for `libcrypto`…)
- Had to correct the relevant user that the recipe was telling pound to build as.
The first point was pretty silly and the second one was just clearly my copy-and-paste mistake.