[Mono-aspnet-list] Is this a serious flaw or just my mistake?

Batchwood jghsurfpro at hotmail.com
Tue Jul 28 12:02:23 EDT 2009


My earlier post and subsequent research regarding virtual hosting has led me
to suspect that Mono may have a serious flaw. Perhaps I’m missing something
very basic, but judging by the absence of replies to my earlier post, maybe
not.

I’m convinced that ASP.net and Mono have a very bright future. ASP.net
removes many of the issues previously associated with writing complex web
applications. As long as Microsoft doesn’t screw it up it’s going to be very
popular.  Mono on the other hand opens this technology up to a much wider
audience. The two are a great combination.

Here’s the issue. In order for Mono to really grab the ASP.net market, it
needs to accommodate the ISP’s. If ISP’s can run their ASP.net web hosts on
a Linux server instead of the much more expensive Windows box, it will be
very beneficial. I’m not an experienced System Administrator, but I haven’t
been able to setup web hosting on Mono. Although setting up multiple web
sites is easy on Mono, setting up web hosts each with their own domain name
(ie www.example.com, www.example2.com etc), isn’t. With Apache, this is done
using VirtualHosts in the apache2.conf file and then setting the ServerName
to the web hosts domain name; however, when I tried this under Mono, Apache
won’t re-start. One poster suggested that this is an Apache problem rather
than a Mono issue, but VirtualHosts works fine in native Apache and it’s the
introduction of the Mono include statement (Include
/etc/apache2/sites-enabled/) that causing the problem so why would the
Apache people know how to fix it?

This is what I’ve tried (using many different variations of syntax):

Sites-available Settings
I followed the Mono documentation like this:
  In a file called example.com, I added
  Alias /example "/var/www/example "
  AddMonoApplications default "/example:/var/www/example "
  <Location /example >
	SetHandler mono
  </Location>
I then run a2ensite exmple and then /etc/init.d/apache2 restart

Sites-available/default Settings
I tried adding this to the default file:
<VirtualHost *:80>
	ServerName www.example.com
	ServerAdmin webmaster at localhost
	DocumentRoot /var/www/example
	<Directory />
		Options FollowSymLinks
		AllowOverride None
	</Directory>
	<Directory /var/www/example/>
		Options Indexes FollowSymLinks MultiViews
		AllowOverride None
		Order allow,deny
		allow from all
	</Directory>
	ErrorLog /var/log/apache2/error.log
	LogLevel warn
	CustomLog /var/log/apache2/access.log combined
    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from 127.0.0.0/255.0.0.0 ::1/128
    </Directory>

I don’t believe that something as well designed as Mono can be missing
something as basic as virtualHosting, so I’m probably doing something wrong.
I’ve spent days researching and experimenting this but have not found a
solution. My concern is that others will be turned away from such a good
technology because they too can’t find an answer. If someone can give me
some direction, perhaps it will not only help me but be a source of
information for others trying to find a solution to this issue.

-- 
View this message in context: http://www.nabble.com/Is-this-a-serious-flaw-or-just-my-mistake--tp24702520p24702520.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.



More information about the Mono-aspnet-list mailing list