You've asked the question and gotten several responses saying that you
either can't do what you want, or that what you want to do can be done much
easier by simply using post-commit hooks to update a working copy that can
be served by Apache. Yet you keep arguing.
If you think all of those responses are wrong, wouldn't it be easier to go
and try it out and if those responses were proved incorrect (unlikely) to
provide this new-found knowledge back to the mailing list?
-----Original Message-----
From: Rainer Sokoll [mailto:r.sokoll@intershop.de]
Sent: Thursday, June 29, 2006 11:00 AM
Cc: users@subversion.tigris.org
Subject: Re: Updating a live website with a post-commit hook script
Greg Thomas wrote:
> On Thu, 29 Jun 2006 15:23:51 +0200, Rainer Sokoll
> <r.sokoll@intershop.de> wrote:
>>What if svn:mime-type is set to application/x-httpd-php?
>
> The MIME type of a file only affects how the client displays it. PHP
> etc. code is processed server side.
[The discussion goes slightly off topic, but I cannot stop myself ;-)]
I disagree.
To my best knowledge:
If you do not have somewhere in your apache config:
"AddType application/x-httpd-php .php" or "application/x-httpd-php php" in
mime.types
then apache will deliver the contents of your php file as text/plain.
If you have one of the statements above, apache will pass the php file to
mod_php (if DSO is supported) and then deliver whatever the php script
returns.
So my question is: Does mod_svn give back its results to apache for further
processing (for example mod_php) or not?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 29 17:57:05 2006