Re: Any way to run two versions of the same perl classes at the sametime?
Thomas Burkholder wrote: Hi there- I've reached a point where I've released a stable version of my project (areaj, at www.areaj.org) with a demo server (www.areaj.org/areaj) but I want to continue development work on the same machine. But, obviously the new and old versions of the code live in an identical namespace - so I don't see a way to run both servers under the same apache installation. I can't just use StatINC and change the code dynamically, because that will create an unpredictable and bug-prone experience for the people using the production server (I want folks using the production server to see the existing product anyway, not what I'm developing on). Does anyone know of an easy way to solve this with apache/mod_perl, without running on two different servers? Locating the code isn't a problem; I already deliver the code to a custom location in the user's home dir. I just don't know how to get two apaches to run that read the different versions of the code. This issue has been discussed many times here, you may want to read the archives, but since you don't need the solution for the production server Apache::PerlVINC should satisfy you:http://perl.apache.org/guide/modules.html#Apache_PerlVINC_Allows_Module mod_perl 2.0 has this problem solved (when it's released) __ Stas BekmanJAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide --- http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
Re: Any way to run two versions of the same perl classes at the sametime?
Hi! You can use this method. Run another apache server in port 8080 (for example) You can't change dir when move script to front server. See - http://www.my_server.com:80/index.html (or http://www.myold.com/index.html) http://www.my_server.com:8080/index.html - developer server. Vlad Chubuk Stas Bekman wrote: Thomas Burkholder wrote: Hi there- I've reached a point where I've released a stable version of my project (areaj, at www.areaj.org) with a demo server (www.areaj.org/areaj) but I want to continue development work on the same machine. But, obviously the new and old versions of the code live in an identical namespace - so I don't see a way to run both servers under the same apache installation. I can't just use StatINC and change the code dynamically, because that will create an unpredictable and bug-prone experience for the people using the production server (I want folks using the production server to see the existing product anyway, not what I'm developing on). Does anyone know of an easy way to solve this with apache/mod_perl, without running on two different servers? Locating the code isn't a problem; I already deliver the code to a custom location in the user's home dir. I just don't know how to get two apaches to run that read the different versions of the code. This issue has been discussed many times here, you may want to read the archives, but since you don't need the solution for the production server Apache::PerlVINC should satisfy you:http://perl.apache.org/guide/modules.html#Apache_PerlVINC_Allows_Module mod_perl 2.0 has this problem solved (when it's released) __ Stas BekmanJAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide --- http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
