Alex,

I've already tweaked some of my .pm's and it's on my mind the changes I've made (for many reasons, not only "improvements").

I want to move the site to SpeedyCGI without reinstalling, so I don't lose these tweaks in my development environment.

Which files do I have to change? Just the db_cgi_path and the /admin directory? Or are there other files?

Then set just one parameter -- persistant environment "on" in the config?



PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://LinkSQL.com/FAQ

You should change *.cgi and then in the ConfigData.pm set persisten_env => 1.

Cheers,

Alex

--
Gossamer Threads Inc.

I'm finding I have to "touch" the scripts fairly often, and even restart apache now and again. I know it has to be a speedy thing, (and I'm running the current version).

I have both the FAQ and Girlfriends.com running under speedy, and I might also make the PostcardsPortal do the same (high-traffic sites, except for the FAQ..) and they take too long to build, so I was using dynamic "static" detail pages. SpeedyCGI seems/seemed to be the solution... but it's one more program to deal with.



PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://LinkSQL.com/FAQ

If you change the cgi scripts, SpeedyCGI should notice and you don't have to do anything, however if you change any of the modules, you need to touch the cgi script to get it to reload.

Cheers,

Alex

--
Gossamer Threads Inc.

Yeah, the modules change regularly... unfortunately. I might need to set up a chron job to touch my scripts every 5 minutes just to be on the safe side... talk about the sledgehammer approach.

PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://LinkSQL.com/FAQ

Only while in development though, as otherwise you lose the benefit of being under a persistent environments (scripts stay compiled).

Cheers,

Alex

--
Gossamer Threads Inc.