Server Requirements:

Linux / Apache Server:

Webbit CMS will run on most Linux/Apache shared hosting environments as long as it does not do agressive page caching (see note below).

Although it will run on non-Unix/Linux servers, our experience with other server platforms has not been positive and we nolonger support any non-Linux, or non-Unix based servers.


Webbit-CMS is written to run using any up to date Unix/Linux version of PHP5.  The package is absolutely NOT compatible with PHP4.

  • We require an up to date version of MySQLi (MySQL Improved) installed to allow PHP5 to commicate with MYSQL5. 
  • All of the Magic Quotes parameters must be set to OFF
  • We require that PHP5 have the ability to create, change, remove files and directories and that APACHE be allowed to follow SYMBOLIC links..


The CMS requires MYSQL5i for its database storage.  For most installations, 1 database with less than 10 tables should be sufficient to run the CMS system.

Of more importance is the number of concurrent connections which are allowed for MySQL.  The number of concurrent connections will limit how many user can be access a website on pages which involve the MySQL database.  These typically include calendars, event listings, blogs, logging in and out of private areas of the website and photo galleries.

The number of MYSQL connections required will depend upon the amount of activity on the website.  Generally 10 to 15 simultaneous connections is sufficient as our publishing system builds static copies of most of the pages to reduce server load as much as possible.

The features which do utilize database connections are: Blog, Calendar, Event Lisitngs, and Private User content requiring a login.

Server Page Caching Issues:

In some shared hosting environments, the operators of those services have turned on aggressive page caching which interferes with the operation of Webbit-CMS as well as many other CMS systems.  

The purpose of caching is to allow the webserver to more efficiently send page content to a user by keeping copies of recently accessed pages in 'cached' memory so that it can can send those pages to the user without having to fetch them again from the server.  This works well as long as the website is not being updated

The downside effect of the caching is that when, for example, you replace an image through the CMS, you may still see the old image even though the webserver has been updated.  Caching improves the performance of the server because it does not have to go back to find the most recent copy of the image of webpage if it has a copy in cached memory.

Some hosting companies allow the caching to be turned off in which case we can work with them.