|laziness, impatience, and hubris|
is there a way to (temporarily) switch off mod_perl caching/variable storing?by tomgracey (Beadle)
|on Jul 10, 2013 at 18:36 UTC||Need Help??|
tomgracey has asked for the
wisdom of the Perl Monks concerning the following question:
I have been trying to run git through apache (ie web based version control) but git is really living up to its name and refusing to cooperate. (Just finished 2 more days of tearing hair out). Now I'm wondering if there isn't some mod_perl weirdness going on.I have found, after (very) lengthy experimentation the simplest way I can get my error is as follows:
What I do is I set up /test/repo so it has files waiting to commit, make sure everything belongs to apache and then fire the script off in the browser.
What I am finding now is that if I run it immediately after restarting apache it works:
... but next time I try it (after deleting the .git folder etc and resetting - but not restarting apache) I get
and it doesn't work from then on. I am wondering if mod_perl isnt responsible for this odd behaviour, ie trying to use a cached value somewhere the second time around. Does anyone know a way I can test this?
Otherwise, any general thoughts on what might be going on?