The web server should be configured to deliver content over HTTPS (via TLS/SSL).
Make sure the server is capable of rendering PHP. On Linux systems most often the installation of PHP enables the
php5_module but you should confirm it has been enabled. The configuration of Apache to use the module and parse
.php files as PHP is also often done when PHP is installed but you should confirm that your Apache configuration contains lines similar to these:
<IfModule mod_php5.c> <FilesMatch "\.ph(p|tml)$"> SetHandler application/x-httpd-php </FilesMatch> <FilesMatch "\.phps$"> SetHandler application/x-httpd-php-source </FilesMatch> </IfModule>
After PHP 5.6, the 5.x numbering has been dropped. Later versions are named (eg)
You may wish to restrict the configuration for parsing of
.php files to the COmanage Registry directory by embedding the
<FilesMatch> element inside of an appropriate
<Directory> element. See the Apache httpd documentation.
Configure the directory holding COmanage Registry to allow symlinks, overrides, and accept
index.php. For Apache, something like the following should work:
<Directory "/path/to/docroot/registry"> Options Indexes FollowSymLinks DirectoryIndex index.php AllowOverride All Order allow,deny Allow from all </Directory>
Make sure that the
mod_rewrite Apache module is installed and enabled.
Under certain circumstances, such as deployments behind a web proxy, it may be necessary to specify the base URL since the application will be unable to introspect it correctly. As of Registry v4.1.0, this can be set via the environment variable