OK, not a straight handler, but 'ScriptAliasMatch'. Like so:
ScriptAliasMatch \.foo*$ "/path/to/helloworld.py$1"
I should be able to hit /a/b/d/e/f.foo in a browser and have helloworld.py
execute, right?
Well, it works just fine when declared at root level (not in a
or directive) and for
Well the code from that blog entry works as reported for
declarations but not for ones where mod_dav_svn is the handler.
I recreate both of those in a single server implementation if I mount the a
svn/ folder inside the canonical docroot (as is common), then play with
URLs that should be
Yup. I'm able to go down a rabbit hole on things, though. I've just spent
an hour trying to find a docker image to start with so that I was able to
ship something that's easily run as an an example for this group. Who knew
there's a *few thousand* ways of configuring Apache in docker images, heh?
Yes, I was also about to suggest mod_rewrite. Should be possible to match on
your secret hidden filename and return content from a “shadow” directory
structure that only contains those files.
You could generate those files in the shadow structure on the post-commit
event.
I have rewrites
"Two docroots" might be what I'm looking for: http://madbean.com/2007/two-
docroots/
The author, Matt Quail, has been Jira lead for a decade, I think.
OK, so most of ye know I am on this quest.
*Context*: I've a working merkle-ish client tracking changes in a Svn
server over DAV, and noting when files directories change and replicating
that change on the client side. For files it gets the SHA1 for the file,
stores it, and updates local file
6 matches
Mail list logo
