Re: Re: Developement and production mod_perl sites on a single server

Doesn't that leave you with whatever modules are in the lib path being used by both processes? How do you maintain a seperate set of modules across the two server instances?

How do you migrate from one set to the other?

Comment on Re: Re: Developement and production mod_perl sites on a single server

Replies are listed 'Best First'.
Re: Re: Re: Developement and production mod_perl sites on a single server by IlyaM (Parson) on Nov 12, 2002 at 00:54 UTC
Doesn't that leave you with whatever modules are in the lib path being used by both processes? How do you maintain a seperate set of modules across the two server instances? Each mod_perl server can use its own lib path. There are many ways to modify default @INC: for example you can set PERL5LIB environment variable in Apache startup script (see perlrun for description of PERL5LIB) or just use lib in server startup script. How do you migrate from one set to the other? Simpliest solution: `cp -rv /home/testing /home/production` what requires you to store all information that varies in production and development environments like filepaths and database name in separate config files. Actually it may be much more complex (say, you want to use CVS). This is the question of deployment strategy which was recently covered by this thread in mod_perl maillist. -- Ilya Martynov, ilya@iponweb.net CTO IPonWEB (UK) Ltd Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net Personal website - http://martynov.org	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Developement and production mod_perl sites on a single server
by IlyaM (Parson) on Nov 12, 2002 at 00:54 UTC

Doesn't that leave you with whatever modules are in the lib path being used by both processes? How do you maintain a seperate set of modules across the two server instances?

Each mod_perl server can use its own lib path. There are many ways to modify default @INC: for example you can set PERL5LIB environment variable in Apache startup script (see perlrun for description of PERL5LIB) or just use lib in server startup script.

How do you migrate from one set to the other?

Simpliest solution: cp -rv /home/testing /home/production what requires you to store all information that varies in production and development environments like filepaths and database name in separate config files.

Actually it may be much more complex (say, you want to use CVS). This is the question of deployment strategy which was recently covered by this thread in mod_perl maillist.

--
Ilya Martynov, ilya@iponweb.net
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

[reply]
[d/l]