Re: tux name based virtual hosting question

You Don't need that line.
The DOCROOT variable is specified in /etc/sysconfig/tux
Edit that file "/etc/sysconfig/tux" and set the DOCROOT to e.g
DOCROOT=/var/www 

Thats it
If you are adding a new domain called newsite.com 
all you do is create a directory in /var/www/ called newsite.com and tux
will automatically detect it as a new domain.


-------Original Message-------

From: [email protected]
Date: Monday, July 15, 2002 03:21:56 PM
To: [email protected]
Subject: Re: tux name based virtual hosting question

thanks. this is great 
now the only remaining question is where do i put the line:


http://www.newsite.com/*.html => $DOCROOT/newsite.com/*.html

do i put it in sysctl.conf under the net.tux.virtual_server section or in
hpptd.conf (or both)?

thanks again.
chris

==========================================
Chris Nuccio                                IT Dept/ Web Dev.
[email protected]                           www.ltpro.com    
Leo Ticheli Productions     v. 205-930-0500 fx. 930-0505
==========================================

----- Original Message ----- 
From: BuildPage, Inc. 
To: [email protected] 
Sent: Monday, July 15, 2002 1:12 PM
Subject: Re: tux name based virtual hosting question


----
sysctl.conf File

---------------
# Disables packet forwarding
net.ipv4.ip_forward = 0
# Enables source route verification
net.ipv4.conf.default.rp_filter = 1
# Disables the magic-sysrq key
kernel.sysrq = 0
fs.file-max=64000
fs.inode-max=128000
# Virtual Server Configuration
net.tux.virtual_server = 1
net.tux.max_connect = 10000

Remember to enable Virtual Mass Hosting in the apache configuration as well
and have them both pointing to the same docroots directory. 

In the httpd.conf have something like this:

VirtualDocumentRoot /var/www/hosting/%0+
VirtualScriptAlias /var/www/hosting/%0+/cgi-bin

Where /var/www/hosting is your document Root. Apache port should be set to
8080

Only problem with Tux I have found is there is no DirectoryIndex derivative.
So by default all requests look for index.html. If it doesn't find this it
returns a 404. index.htm cant be defined. With apache however you can define
what the standard start file is. Secondly I have not yet figured out how to
prevent hotlinking with tux as it caches static pages

-------Original Message-------

From: [email protected]
Date: Monday, July 15, 2002 02:50:52 PM
To: [email protected]
Subject: tux name based virtual hosting question

hi,
i have tux 2.0.26 set up and running (and apache as dynamic secondary server
 albeit unused at the moment). only one site on it now.
i want to add some more sites to this box, preferably sharing the same IP. i
have searched google and redhat, now onto the
forums....

i found http://people.redhat.com/mingo/TUX-patches/2.1-docs/virtual-hosting
html that is the closest i have found to what i need.
however it doesn't have an example of syntax. how do i enter these tunable
variables into /etc/sysctl.conf?

for example: (from the above link)
===================snip================

There are three tunables that deal with virtual hosting:


a.. virtual_server - Valid values are 0, 1, 2, or 3.

b.. mass_hosting_hash - Valid values are 0, 1, 2, or 3.

c.. strip_host_tail - Value must be an integer.

These three tunables depend on each other, and the strip_host_tail tunable
is only used if host based virtual serving is enabled.
Otherwise, it is ignored.

virtual_server
If the value is set to 0, virtual hosting is disabled:

http://www.example.com/a.html => $DOCROOT/a.html


If the value is set to 1, host-based virtual hosting is enabled:

http://www.some.site.com/a.html => $DOCROOT/some.site.com/a.ht?ml


=========snip==================
so first i make a user directory in the doc root (e.g. var/www/html/newsite)
so in /etc/sysctl.conf would i put:

virtual_server = 1
http://www.newsite.com/*.html => $DOCROOT/newsite.com/*.html

or simply by virtue of using names in the entry does it assume mode 1?

must i specify each html page as an entry (as in /a.html above) or will the
wildcard (*)in the above work?

and is virtual host set to (equal sign) 1 or (=>) or what?

and don't i have to label the section "virtual host" (or #virtual_host)?

i'd really just like to see an example of /etc/sysctl.conf from a working
setup (fake names/ IP's of course)
then i would feel safe trying it on the now live and critical server.
i have no other box with tux/apache setup to test so i a bit leery. new to
tux in june.
thanks for any help.

==========================================
Chris Nuccio IT Dept/ Web Dev.
[email protected] www.ltpro.com
Leo Ticheli Productions v. 205-930-0500 fx. 930-0505
=============================================================================
======
Chris Nuccio IT Dept/ Web Dev.
[email protected] www.ltpro.com
Leo Ticheli Productions v. 205-930-0500 fx. 930-0505
==========================================




_______________________________________________
tux-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/tux-list
.