Trouble with the "Setting Up and Maintaining a Centralized concrete5 Installation" how to

Permalink
Hi There,

I've been following along with this How To and have done the following so far:
- Uploaded the latest c5 to: /path/to/webroot/c5/concrete5.4.2.1/
- Deleted all directories except /concrete
- Chose not to use the "concrete-latest-stable" symlink
- Chose option two and added an Alias to the virtual host

The the php_value include_path uses a path to a pear directory in the How To:
php_value include_path ".:/usr/share/pear:/home/c5/concrete5.4.2.1/concrete"


But I don't have a pear directory - is pear software that makes this all work and is it this?:http://pear.php.net/

I then saved my virtual host file, reloaded apache and renamed the /concrete directory in the test site to see if the Alias was working - but no luck.

I'm not too technical when it comes to virtual hosts, so maybe I have a conflict:
<VirtualHost *:80>
   ServerAdmin webmaster@localhost
   ServerName test-site.domain.com   
   DocumentRoot /path/to/webroot/test-site
   # --------------------------------------------------------------------------   
   # CENTRALISED C5 INSTALL SETTINGS
   Alias /concrete /home/c5/concrete5.4.2.1/concrete
   php_value include_path ".:/usr/share/pear:/home/c5/concrete5.4.2.1/concrete"
   # --------------------------------------------------------------------------   
   <Directory />
      Options FollowSymLinks
      AllowOverride None
   </Directory>
   <Directory /home/steelpipe >
      Options Indexes FollowSymLinks MultiViews


Can anyone see where I've gone wrong? Any suggestions welcome!

Cheers

Ben

 
cmscss replied on at Permalink Reply
Hmmm, found a /pear directory inside /etc/pear so updated the include path to:
php_value include_path ".:/etc/pear:/home/c5/concrete5.4.2.1/concrete"


But still no luck

This website stores cookies on your computer. These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Privacy Policy.