Shared Blog Installation

[greenie]

Hello!

I would like to run a shared blog installation on my BH domain. I have a primary domain alongside a few add-ons.

The directions from the blog developers say to put one primary blog installation in "/usr/local/lib/php/Blog/" so that all my add-ons can then have their own separate templates/db/etc. I don't have permissions to "/usr/local/lib/php/" on BH, but can technically run a local version of that spot, right? In my home directory?

So on a BH shared host installation, I take it that would mean installing an PEAR package via the cpanel. That would create my own local home/username/php directory where local PEAR stuff can live. Then I would just treat that as my local php include_path, and put my "Blog" directory alongside the PEAR directory, and distribution files in there.

Then I would just need to put this in my php.ini:

include_path = ".:/usr/lib/php:/usr/local/lib/php:/home/yourusername/php" ;

Seems like that would do it "in theory". However, I noticed that in the BH control panel they mention only full PEAR packages can be installed, no betas. Would I be breaking any type of rules by pursuing the shared blog installation I mentioned above (ie. putting a "Blog" directory inside of "home/username/php")? I don't want to do anything that will get me kicked out of BH ;) I don't need a shared installation that bad.

[php8ox]

I think on bluehost now, my PEAR junk is in /home/username/php and is already by default referenced in the php.ini file.
I found a ffmpeg binary once upon a time and ran it from that same folder. I have previously hardlinked a PEAR package from another location but that was because I didn't know how to do it the right way before. shouldn't have to modify your php.ini for PEAR - and it's super-easy using the C-panel PEAR installer (or command line on your home testing server?).

Beta, Alpha or any PEAR packages (I believe) can be used if you get them yourself:
http://pear.php.net/ :: and grab whatever you want...