RE: [cobalt-users] SSL setup - Jeff can you help :-)

["Rick Ewart" <cobalt@xxxxxxxxx>]

> In your email you say:
> 
> <snip>
> We don't do it with links at all; here's what we do...
> We create a subdirectory under (for example)
> /home/sites/secure.example.com/web/ for each domain.  For example, for
> our customer with a website at "www.example2.com" we set up the
> following subdirectory:
> /home/sites/secure.example.com/web/example2.com/
> Then we create a new user for example2.com, for example user
"newuser".
> Then we manually edit /etc/passwd to change newuser's home directory
> from:
> /home/sites/www.example2.com/users/newuser
> to:
> /home/sites/secure.example.com/web/example2.com
> </snip>
> 
> Can I ask a really stupid question, how do I get the name
> secure.example.com - is this a sub domain of my main RAQ account which
is
> www.matrixhosting.co.uk which has a self written certificate installed
for
> use by the RAQ GUI.
> 
Having a domain such as secure.domain.com is known as a third level
domain (as opposed to domain.com being a second level domain and .com
being a top level domain). It is not really related to any other domain
(including domain.com), except within DNS. There is no reason it even
has to be on the same system, and often isn't (in the case of big
enterprises).

You would setup another virtual site on your system, but when it asks
for the host name, instead of www, put secure or whatever you want to
call it.

Then you will need to appropriate DNS records too. You might want to
setup an alias of www.secure.domain.com just in case anyone decides to
try it (hard to break the habit of www).

Just FYI, if you SSH'd into domain.com and created a folder called
secure, it would be accessed by www.domain.com/secure, NOT
secure.domain.com.

Hope that helps the confusion a bit....
Rick