Tiki is collaborating with Bluehost to make Tiki run as smoothly as possible. This also generates revenue for the Tiki Software Community Association. (if you subscribe via the link below)

http://bluehost.tiki.org/ is used by Tiki developers.

We are in process for the Bluehost Open Source Service (BOSS)

Our main tech contact is: Jared Smith

Todo

• Test TRIM

Setting file permissions

When running "bash setup.sh" from the command line there will be warnings about not being root or being on a shared server. However, using the f option to "fix the file permissions will work. Just specify your Bluehost account username as the group name when prompted (instead of nobody).

Installation via Tiki packages only recommended installation way for now on Bluehost shared servers

Installation via Tiki packages from our Download page is the only recommended way to install on Bluehosts at the moment. Other methods such as Bluehost's installer that users SimpleScripts is not recommended as it offers an outdated version of Tiki (we are in the process of contacting them to rectify it), and installation from an SVN checkout, that requires the use of Composer might not work because many of Bluehost's shared servers have command line PHP that runs really old versions, e.g. version 5.2.

Running php -v will show you the current version and you can try and look for other versions.

php -v
ls /usr/bin/php*

You will find versions such as /usr/bin/php56s which are not the CLI versions. Thus, they are of no help at all.

Therefore, it is NOT possible to install Tiki via the SVN checkout and composer for Bluehost. There is no point in trying to alias php to a version such as /usr/bin/php56s . If you execute:

/usr/bin/php56s  -v

you will see something like "PHP 5.6.17 (cgi-fcgi)" - the cgi-fcgi part of it tells you it is of no use for use on the command line and will not work with Composer.

When you contact Bluehost customer support about it, they will tell you that the PHP version is fine (but that refers to the PHP version when connecting through the web - you can verify this by putting a info.php file as shown below and accessing it through your web browser) and that they do not support command line. Note also that the PHP version shown on your cPanel might be inaccurate. The most accurate way is to check using the info.php shown below to determine the web version, and also check the command line version via "php -v".

Can't get composer

[~/www/bluehost/trunk]# sh setup.sh
Status: 404 Not Found
Content-type: text/html

No input file specified.
We have failed to obtain the composer executable.
NB: Maybe you are behing a proxy, just export https_proxy variable and relaunch setup.sh
1) Download it from http://getcomposer.org
2) Store it in temp/

The solution is to manually download the latest composer.phar and put it in the temp/ folder in your Tiki installation. You can manually get it from the http://getcomposer.org site, probably http://getcomposer.org/Download and then transfer it to the temp folder, or you can execute the following when in your Tiki root folder:

curl https://getcomposer.org/composer.phar > temp/composer.phar

However, if you also have the PHP version problem then you won't be able to install via composer.

Feedback from test account

• To discuss: http://bluehost.tiki.org/tiki-check.php
  • How to get fileinfo
• See SimpleScripts
• If files are unzipped from a downloaded .zip (to a subdirectory, not sure if this makes a difference), sh setup.sh needs to be ran or you get error 500. So how can we set file permissions in the zip to avoid this?