Getting WIAB on a web server

WIAB is tested with the Apache and Lighttpd web servers running under FastCGI. It should also work with any other web server that supports FastCGI (for example nginx or IIS) but these are untested.

If you are using Catalyst version 5.7008 or later, you are able to deploy on server root (http://example.com) or off server root (http://example.com/mysite). Earlier versions of Catalyst (5.7 or later, and possibly the 5.6 family) should run WIAB on server root, but will not work properly when deployed on a subdirectory.

Deployment can be fairly complicated, as you're relying on the behaviour of multiple different software systems on what could be any of a number of operating systems. Therefore we will make some recommendations below.

Deployment Recommendations.

Remember that you can test your deployment using WIAB's live server automatic test routines explained in the Installation section. Use these tests to confirm that your site will work as expected.

If you are using WIAB on your own fresh webserver, and you aren't a system administrator, we recommend that you use Lighttpd as it is small and efficient software, has FastGCI built in, is fairly simple under the hood. This all means that there's less that can go wrong. You can confirm that your local installation of lighttpd is going to work for you by issuing the following command from the WIAB root directory (remember to use the wiab_local.yaml file not your own configuration):

If you have access to a shared server with the Apache web server, you are going to need to get your system administrator to set up FastCGI for you. If you can, get your sysadmin to install Catalyst for you as well.

Please see the Apache and Lighttpd pages for example configuration instructions.

Menu

Navigation

powered by website in a box