From owner-freebsd-python@FreeBSD.ORG Fri Jun 3 16:02:01 2005 Return-Path: X-Original-To: freebsd-python@freebsd.org Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D49F216A41C for ; Fri, 3 Jun 2005 16:02:01 +0000 (GMT) (envelope-from gedge-lists@yadn.org) Received: from turner.cymru.serf.org (cpc3-cdif5-5-0-cust135.cdif.cable.ntl.com [82.22.34.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64BBB43D54 for ; Fri, 3 Jun 2005 16:01:54 +0000 (GMT) (envelope-from gedge-lists@yadn.org) Received: from gedge by turner.cymru.serf.org with local (Exim 4.51 (FreeBSD)) id 1DeEcL-000O80-Mv for freebsd-python@freebsd.org; Fri, 03 Jun 2005 17:01:53 +0100 Date: Fri, 3 Jun 2005 17:01:53 +0100 From: Geraint Edwards To: FreeBSD python list Message-ID: <20050603160153.GA56758@cymru.serf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organisation: Caerdydd, Cymru / Cardiff, Wales X-MotD: "Progress is that which has caused Usenet to go from smart people in front of dumb terminals, to dumb people in front of smart terminals" -- sig Subject: new to python/zope - installation woes X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 16:02:02 -0000 Hi, I have a customer that wants to run their website on Plone, They've delivered me a *.zexp file and a products.zip file. I just want to throw it on my 4_RELENG server - and forget about it. I installed Plone (and hence Zope and python!) from ports (you will soon deduce, if you haven't already, that I am new to all three!). What follows is some feedback (meant as constructive criticism) from a someone who has acquired a big headache. Firstly, if you install the www/plone port, it installs www/zope, and the "critical" instructions for make instance [...] are scrolled into the ether and their importance is missed, and thus began my headache. Your install might not scroll them off, but my ports database is full of bsdpan-* crud that fills my screen up with junk, so I don't necessarily realise that zope is installed (hey, plone is what I wanted, right?). Anyway, I scrolled back and found the zope instructions and ran make instance INSTANCENAME="foo" and make instance INSTANCENAME="bar" because I want to test this in 'bar' before making things "production" in 'foo'. I made the zope.conf files, too, setup rc.conf with: zope_enable="YES" zope_instances="/usr/local/www/Zope/foo /usr/local/www/Zope/bar" and ran "zope.sh start" - so far so good. However, 'bar' never gets any logs - it all seems to go to .../foo/log/... and the logs don't get anything interesting in them when things go horribly wrong (see later). After *much* playing with Apache to get it to proxy for zope, I was getting bitten by the annoying