mlstill.blogg.se

(mod_mono can handle non-ASP.NET pages as well. Lines 3-5 instruct Apache that absolutely all files in the /test virtual path are to be handled by mod_mono. The second line creates an ASP.NET application in something other than the root virtual path. The Alias directive is a standard Apache directive to map a virtual path to a physical path. Unlike the first example, this example assumes that the virtual path “/test” does not already correspond to the physical path /usr/share/doc/xsp/test. Edit your nf file (hint: /etc/httpd, /etc/apache2) and append the following lines (remove the numbers  -):

Let’s say you want those file to be available under the virtual path /test. Here is another configuration that sets up the ASP.NET test suite that comes with mod_mono. extensions (or whatever was specified in AddHandler) based on the physical path provided in the MonoApplications directive. This is important because in that virtual path, Apache itself will continue to serve images, static HTML, and other files, based on the physical path it knows in DocumentRoot, while mod_mono will handle files with. at ), and that this virtual path corresponds to the physical path on disk of /home/username/So if the virtual path is /, as in this example, the physical path matches what is in the DocumentRoot directive for Apache. The third line instructs mod_mono that an ASP.NET application exists at the root directory of the web site (i.e. extensions should be delegated to mod_mono (rather than Apache processing them itself as plain-text files). The second line instructs Apache that processing of files with. (If inside a VirtualHost section, it disables it just for that virtual host). The first line disables the AutoHosting feature. They can just go at the end, or inside VirtualHost sections.Ī basic setup is as follows (with line numbers added for convenience): Further, it is important (as of Mono 1.2.5) to place the remaining mod_mono directives after the User and Group directives. The following assumes you have included mod_nf in your main configuration file as described above. When AutoHosting does not fit your needs, you will need to include several mod_mono Apache directives in your main Apache configuration file (often /etc/httpd/conf/nf, or the like in /etc/apache2) to get the site running. Unfortunately, PHP seems to not necessarily work with the MPM, so you may not be able to go this route. It is advisable to use the MPM with mod_mono. That module implements a mixed process/thread model which spawns several processes as well, but each of them can create a configurable number of service threads. Another module usually available with your distribution is the MPM. The one installed by default by most distributions is the MPM which implements the traditional, one OS process per server, model and is the same what in the earlier Apache versions.