Okay here is another one :-)
Once zope is installed in /opt/zope-2.7.0 can it be moved without
damaging the install .... say to
In our hosting setup some things get run in a chroot, some things
Currently zope get's installed in a chroot environment for anyone who
wants a zope install. It must be a complete install since when the user
restarts it he will be in his chroot environment.
So I'd ideally like to install zope in a way where all of the core of
zope is in one place ... say ... /opt/zope/<version #> (/opt/zope/2.7.0,
This I can hardlink/symlink into each chroot and make permissions 755
>From there I would like to be able to install an 'instance', which is
... in my case meaning the data.fs, /Products directory, log files, etc,
etc. The stuff that make this users instance theirs. When the install is
happening, the script executing it would most likely be outside of the
chroot ... but I guess it could be configured to chroot as well..
I already have start/stop scripts to go through the users that have a
zope install and chroot into that users 'host' and then start zope as
that 'hosts' administrative user.
On Mon, 2003-03-10 at 21:47, Chris McDonough wrote:
> On Mon, 2003-03-10 at 22:13, Edward Muller wrote:
> > Hopefully I'll get to play with this later on in the week..
> > But here are the things I know I need as part of my business:
> > -The ability to specify which python to use to build, install and run
> > zope with. Our production machines have various version 1.5.2, 2.1.X,
> > 2.2.X, etc installed. I must be able to specify the location.
> ./configure --with-python=/path/to/your/python
> > -The ability for each instance to have separate Product directories.
> > Some users want plone, some don't. Some develop their own software.
> This is inherent in INSTANCE_HOME behavior. The result of
> "mkzopeinstance" will contain a Products directory which may contain
> Zope software. Many instances can be configured to run from a single
> software home (a software home is the result of "make install")
> > -The ability to start/stop zope without access to /proc (or the
> > equivalent on other unices) on Linux.
> > I don't know if the changes made affect any of the above ... but it
> > would suck major #$W%% if it did. Oh, and part of my business if hosting
> > zope ... if you are wondering where the above (off the top of my head
> > list) comes from. Other than that it looks like the changes will be good
> > for me.
> > Oh and some way to have multiple zope versions installed at the same
> > time would be great as well. :-)
> In a Zope 2.7.0 source directory:
> ./configure --prefix=/opt/zope-2.7.0
> make install
> In a Zope 2.7.1 source directory:
> ./configure --prefix=/opt/zope-2.7.1
> make install
> ... then 'mkzopeinstance' from either.
> - C
> Zope maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
Interlix - President
Web Hosting - PC Service & Support
Custom Programming - Network Service & Support
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -