I''d like to give Zope a test drive and I was curious if anyone out there is currently using Zope 2.7 on CentOS 3.4 http://dag.wieers.com/packages/zope/ Dag''s packages seem to be targeted for RHEL4. Worst case scenario, I''ll move one server to CentOS4 but I thought I would ask on the list before upgrading. Thanks, Avtar
Avtar Gill wrote:> I''d like to give Zope a test drive and I was curious if anyone out > there is currently using Zope 2.7 on CentOS 3.4 > > http://dag.wieers.com/packages/zope/ > > Dag''s packages seem to be targeted for RHEL4. Worst case scenario, > I''ll move one server to CentOS4 but I thought I would ask on the list > before upgrading. > > Thanks, > > AvtarZope.org: "Zope 2.7 requires Python 2.3.2 or later. Zope versions 2.5 and 2.6 require a Python 2.1 version equal to or greater than 2.1.3" Centos 3.4 only has Python 2.2.3. If you want to run Zope 2.7 you can build yourself a python from the source code. I have built one of these so far, and I built it so that the python, zope and zope instance were all in the same directory. For instance: /home/user/zope I don''t have a document describing the process, which was a bit involved at times. Running it on Centos4 would be quite a bit easier. -Mike
On Mar 20, 2005, at 19:37, Michael Best wrote:> Zope.org: "Zope 2.7 requires Python 2.3.2 or later. Zope versions 2.5 > and 2.6 require a Python 2.1 version equal to or greater than 2.1.3" > > Centos 3.4 only has Python 2.2.3.As a side not, if you intend to run Zope "in production" it is always *very wise* to compile a separate Python for it. I''ll go one step further and say when it comes to Zope it''s always better to compile from source and not use any pre-packaged version. It''s easy, and when you ask for support on the Zope mailing list you won''t get blank stares because no one can know what each packager does to the Zope software to package it. I''m for using RPMs for almost anything, but never ever for Zope (and by extension the Python you run it on). jens
Michael Best wrote:> Zope.org: "Zope 2.7 requires Python 2.3.2 or later. Zope versions 2.5 > and 2.6 require a Python 2.1 version equal to or greater than 2.1.3" > > Centos 3.4 only has Python 2.2.3. > > If you want to run Zope 2.7 you can build yourself a python from the > source code.Forgot to mention that I noticed that requirement after going through zope.org and Dag''s spec file. I planned on installing a newer version of Python in /opt to keep it segregated from the default CentOS version.> Running it on Centos4 would be quite a bit easier.I''m testing CentOS4 on one box but all the others are running 3.4 - I would prefer to stick with one release across the board. I find that it''s easier to manage servers that way. Regardless, I''d be willing to make an exception if the end result is worth it.
Avtar Gill wrote:> Forgot to mention that I noticed that requirement after going through > zope.org and Dag''s spec file. I planned on installing a newer version > of Python in /opt to keep it segregated from the default CentOS version.Back when Zope was still releasing binary releases with Python included, I used those for a number of hosts, it made it simpler to keep separate versions of database adapters specific to individual sites (psycopg) so that an upgrade to one site''s database adapter was isolated to that site only.>> Running it on Centos4 would be quite a bit easier.Okay that was only a suggestion if you weren''t up to compiling Python. Like I mentioned, I actually put the python, zope and instance all in one directory for a project, I will probably be rolling out 2 or 3 more with the same layout as well. -Mike
Jens Vagelpohl wrote:> As a side not, if you intend to run Zope "in production" it is always > *very wise* to compile a separate Python for it. I''ll go one step > further and say when it comes to Zope it''s always better to compile from > source and not use any pre-packaged version. It''s easy, and when you ask > for support on the Zope mailing list you won''t get blank stares because > no one can know what each packager does to the Zope software to package it.Thanks, that''s a valid point. I usually try my best to stick with vendor provided packages in order to take advantage of security updates. I guess I''ll compile Zope and Python myself so that I can start testing.
On Mar 20, 2005, at 21:52, Avtar Gill wrote:> Michael Best wrote: > >> Zope.org: "Zope 2.7 requires Python 2.3.2 or later. Zope versions 2.5 >> and 2.6 require a Python 2.1 version equal to or greater than 2.1.3" >> Centos 3.4 only has Python 2.2.3. >> If you want to run Zope 2.7 you can build yourself a python from the >> source code. > > Forgot to mention that I noticed that requirement after going through > zope.org and Dag''s spec file. I planned on installing a newer version > of Python in /opt to keep it segregated from the default CentOS > version.Get Python 2.3.5 for any Zope 2.7 version, you might have seen that recommendation in the docs already. 2.3.4 is mandatory, but 2.3.5 is also recommended. Python 2.4 is *not* recommended. jens
Avtar Gill wrote:> I''d like to give Zope a test drive and I was curious if anyone out there > is currently using Zope 2.7 on CentOS 3.4I''m running Zope on 127.0.0.1:8080 and then using Apache ProxyPass and VirtualHostMonster to run my site, here is my quick howto on building zope and python and psycopg. (just my notes, so it might not have too much polish). Building a Modern Zope 2.7.5 + Python 2.3.5 wget http://www.python.org/ftp/python/2.3.5/Python-2.3.5.tar.bz2 wget http://www.zope.org/Products/Zope/2.7.5/Zope-2.7.5-final.tgz mkdir /home/user/zope Python tar -xvjf Python-2.3.5.tar.bz2 cd Python-2.3.5 ./configure --prefix=/home/user/zope make make install Zope tar -xvzf Zope-2.7.5-final.tgz cd Zope-2.7.5-final ./configure --with-python=/home/user/zope/bin/python --prefix=/home/user/zope make make install Create the Zope Instance /home/user/zope/bin/mkzopeinstance.py Directory: /home/user/zope Username: admin Password: adminpassword Egenix MxDateTime wget http://www.egenix.com/files/python/egenix-mx-base-2.0.6.tar.gz tar -xvzf egenix-mx-base-2.0.6.tar.gz cd egenix-mx-base-2.0.6 /home/user/zope/bin/python setup.py build /home/user/zope/bin/python setup.py install Psycopg wget http://initd.org/pub/software/psycopg/psycopg-1.1.18.tar.gz tar -xvzf psycopg-1.1.18.tar.gz cd psycopg-1.1.18 ./configure --with-python=/home/user/zope/bin/python --with-postgres-libraries=/usr/lib/pgsql --with-postgres-includes=/usr/include/pgsql --with-mxdatetime-includes=../egenix-mx-base-2.0.6/mx/DateTime/mxDateTime --with-zope=/home/user/zope make install make install-zope Edit $INSTANCE_HOME/etc/zope.conf effective-user user <http-server> # valid keys are "address" and "force-connection-close" address 127.0.0.1:8080 # force-connection-close on </http-server> #<ftp-server> # # valid key is "address" # address 8021 #</ftp-server> Startup Script $INSTANCE_HOME/bin/zope_ctl Add a chkconfig stanza at the beginning: # zope Start/Stop the Zope web-application server for a particular domain # # chkconfig: 345 95 10 # description: zope is a web server specifically for handling \ # HTTP requests to the Zope web-application service. ln -s /home/user/zope/bin/zopectl /etc/init.d/zope.user chkconfig zope.user on -Mike