Ok, we now have a fresh new 64 bit paravirtualized Debian 4.0 (Etch) virtual machine running on SparKPLUG. It's currently called "newspark" and has an IP of 206.251.247.136.

I have created accounts on it for John and Tracy, because those are the only two who have replied to me in the ##sparkplug channel. :) Neil, Stewart, Jim, etc. please catch me in the channel or email me your SSH public keys and I'll set you up with logins as well.

The Debian install is as bare as can be - done with debootstrap, and I've only added enhanced vim, sudo and SSH since. I suppose we simply need to install and configure Apache/Zope/Plone, Postfix and Mailman and then migrate data.

Let's start with Zope and Plone since they're heavier on resources and are suffering from the speed of the old sparky image. This is probably going to require some more Plone hacking due to version updates again... here's the situation, perhaps Jim or Tracy would like to give me some guidance and tackle any issues that come up:

Currently SparKPLUG is running Zope 2.8 and Plone 2.1.4. The Zope package was provided by Debian, and we put our own Plone in from tarball.

On Debian 4.0, we have available to us Zope 2.9 and Plone 2.5.1 through the packages. It's going to be hard to use anything older, so we're at least going to have to work through an upgrade of our site from Plone 2.1 to Plone 2.5. That may not be too bad - I think Jim probably got a lot of the issues squared away in the previous 2.0 to 2.1 migration.

But the question is... Plone is currently at version 3.0.1 which is meant to run on Zope 2.10. Does that particular setup provide us any further benefits that would make it worth using? Or can we just happily cook along with the 2.9/2.5.1 that Debian gives us?

This is of course not a permanent decision... I'm leaning toward just plopping in 2.9/2.5.1 and migrating to that for now. We can always upgrade again to 3.x when we decide that we need some sort of feature.

If everyone is in agreement, I'll be happy to do the initial Plone and Zope install, get them working from behind Apache, and move our site database over. I'll do this with a test site, and we'll see if there are any issues that need to be handled.

--
Joshua Penix                                http://www.binarytribe.com
Binary Tribe           Linux Integration Services & Network Consulting


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer

Reply via email to