[Mono-list] Problems with mod_mono
Mon, 13 Jan 2003 19:04:44 +0100
.NET deployment model is simple "xcopy" (which means copying the whole
directory to web server). I've been using it for some time, and it really
seems to work.
You just copy source/binary/web.config file and that's all. I cannot come up
with anything more simple than that.
Thanks to shadow directories for DLLs there are no problems with locked
files anymore. No more annoying IIS restarts, looks like MS finally did it.
P.S. There are actually things you can't achieve with web.config. For things
like increasing maximum page execution timeout you still have to modify
"machine.config". But for me it's ok.
----- Original Message -----
From: "Philippe Lavoie" <firstname.lastname@example.org>
To: "Miguel de Icaza" <email@example.com>; "Jaroslaw Kowalski"
Cc: "Fawad Halim" <firstname.lastname@example.org>; <email@example.com>
Sent: Monday, January 13, 2003 5:29 PM
Subject: RE: [Mono-list] Problems with mod_mono
Out of curiosity, what is the model used by Java for JSP pages? They
have an easy way to deploy web applications inside a web server nowdays.
Wouldn't C# be able to use a similar framework?
C# stole so much from Java, we might as well steal their deployment
model too, right? :)
From: Miguel de Icaza [mailto:firstname.lastname@example.org]
Sent: Monday, January 13, 2003 10:55 AM
To: Jaroslaw Kowalski
Cc: Fawad Halim; email@example.com
Subject: Re: [Mono-list] Problems with mod_mono
> Got the same problem. I solved it (partially and temporarily) by
> chmod 0777 /var/www
> (which is obviously the WRONG WAY to do it).
> Afterwards, I got a lot of errors like "finalization cycle involving
> in "httpd/error_log", which I couldn't get rid of.
> Anybody can help?
We should probably have mod_apache set the HOME environment variable to
a directory where the Apache has write permission.
Mono-list maillist - Monofirstname.lastname@example.org