Re: [cobalt-users] Cloaking

[Lyle Scheer <lyle.scheer@xxxxxxx>]

Jamie Martino wrote:

> > The end result would be:
> >
> > thesupermanmovie.com cloaked/redirects to mymaincomicsite.com/sumovie end
> > user only sees-> thesupermanmovie.com
> > thespidermanmovie.com cloaked/redirects to mymaincomicsite.com/spmovie
> end
> > user only sees-> thespidermannmovie.com
> > thebatmanmovie.com cloaked/redirects to mymaincomicsite.com/bmmovie  end
> > user only sees-> thebatmanmovie.com
> >
> > To be clear, the user NEVER sees mymaincomicbook.com/subdirectory, they
> only
> > see the contents of the directory and the browser displays the domain
> names,
> > thesupermanmovie.com thespidermanmovie.com and thebatmanmovie.com
> >
> > Is this in fact done in the httpd.conf file and are there any special
> > instructions?
>
> Yes, after you setup the domain in the GUI telnet into your box and find the
> <VirtualHost> entry for each domain, ie thesupermanmovie.com, and change the
> following line
>
>                     DocumentRoot /home/sites/site13/web
>
> Change it to whatever directory you want, for instance, if mycomicsite.com
> is at "/home/sites/site1/web" then change the above line to:
>
>                     DocumentRoot /home/sites/site1/web/sumovie
>
> Then save the httpd.conf file and restart the webserver with:
>
> /etc/rc.d/init.d/httpd restart
>
> Not sure if this voids the warrenty, but all documentation says it does..
> Call Cobalt and ask them, I did it anyways...  :) Hope this helps ya..

Save your old httpd.conf file, or be able to back out your hand changes if you
want to call Cobalt warranty support. IE... you'll only get unsupported if Sun
Cobalt support figures out that you've edited it:

You:  Support guys!  my web pages aren't working!
Support guy:  Well then, let me take a look... hmmm... http.conf... wait,
what's this.  It looks like you've hand edited your configuration file.  We
can't support that.  Sorry.

In other words, Cobalt cannot debug the plethora of things that could possibly
go wrong if a well intentioned user starts modifying the system by hand.
Cobalt support is trained to handle how the system functions when the Cobalt UI
modifies those files.  Thus, the warranty is void if you make any such
modifications.

Therefore, I highly recommend that any hand edits you create, that you give
yourself a way to back them out to vanilla, and check to see if your problem is
still there.  If it is, support will attempt to deal with how the Cobalt UI
modified things such that it got into a wedged state.  Even this can be a
problem if your hand edits cause the UI to do something it wouldn't normally do
when you then go change something using the UI.  IE.  you modify the
configuration file, then add a site and the add site gets confused by your hand
edits and adds the site incorrectly.  To be totally safe, you should back out
any hand edits before you use the UI to do anything.

Alternately, you can pay the $200 an hour rate to our professional services
staff to make modifications for you that they will support on your product.
They have an understanding already of what the UI does and have a better chance
of making a good modification than just randomly changing something and hoping
for the best.  That price tag also pays for the responsibility of professional
services to fix it if it ever messes anything up.

Alternately, you might find a knowledgeable reseller or 3rd party person
willing to make changes and take responsibility for cheaper.

The cheapest method of change is to make the change yourself and take on the
responsibility yourself.  This incurs the highest risk to you personally.  One
way to reduce this is to ask around in support forums like this for other
people who have made similar changes and their experience, and that is what you
have done.

I hope this helps!

- Lyle