[BlueOnyx:06338] Re: Cpanel to Blue Onyx move

[Darrell D. Mobley]

> -----Original Message-----
> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> On Behalf Of Darrell D. Mobley
> Sent: Wednesday, January 19, 2011 7:51 PM
> To: 'BlueOnyx General Mailing List'
> Subject: [BlueOnyx:06337] Re: Cpanel to Blue Onyx move
> 
> > -----Original Message-----
> > From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> > On Behalf Of Ken - Precision Web Hosting, Inc
> > Sent: Wednesday, January 19, 2011 7:23 PM
> > To: BlueOnyx General Mailing List
> > Subject: [BlueOnyx:06336] Re: Cpanel to Blue Onyx move
> >
> > You could create a directory like
> > https://secure.somesecuresite.com/www.newsite.com/
> > or a better option is to gget rid of the www as below.
> > https://secure.somesecuresite.com/newsite.com/
> > Some security software installs don't like the extra www. in the url and
> > give a phishing warning.
> >
> > Create a directory like that for each site.
> > Then in the /etc/httpd/conf/vhosts/sitexx  for secure.somesecuresite.com
> > you could add a directive like
> >  the one below for each directory.
> >
> > <Directory /home/.sites/132/site21/www,newsite.com/>
> > #only one line below
> > php_admin_value open_basedir
> >
> /home/.sites/132/site21/web/newsite.com/:/home/tmp:/tmp:/usr/bin/pear:/hom
> > e/solarspeed/php/bin/pear:/usr/share/pear
> > #only one line above
> > </Directory>
> >
> 
> Would it work if I used a symbolic link instead of an actual directory?  I
> would have to add "AllowOverride" and "Options All" as well, right?

I was able to get it working using a symlink by editing the site1.include
file:

# /etc/httpd/conf/vhosts/site1.include
# user customizations can be added here.
<Directory "/home/.sites/28/site1/web"> 
	AllowOverride All 
</Directory>

And then adding the new site's path to its web directory to GUI open_basedir
settings for site1.

Riddle me this:

I have another site on this server that has an include file that looks like
this:

# /etc/httpd/conf/vhosts/site4.include
# user customizations can be added here.
<Directory "/home/.sites/70/site4/web">
   AllowOverride All
   Options All
</Directory>

And HTTPD runs fine.  If I add "Options All" to site1's include file, I get
this error:

[root at web1 vhosts]# service httpd restart
Stopping httpd: [  OK  ]
Starting httpd: Syntax error on line 5 of /etc/httpd/conf.d/ssl_perl.conf:
$parms->add_config() has failed: Option All not allowed here at
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Apache2/PerlSection
s.pm line 203.\n
[FAILED]

Options All is not set for the overall server in the GUI, but otherwise the
settings for site1 and site4 are virtually identical.  Why adding "Options
All" to site1.include causes HTTPD to fail but not site4 is a head
scratcher.

It's the oddest things, like in the virtual site list in the GUI, when I
sort sites by Full Host Name, for the life of that server, it cannot list
the sites alphabetically.  Weird.