Previous | Next | Up | Table of Contents

5.3. Special Files

Package files requiring user configuration can be specified, and scripts nominated to be executed when a package has been installed or configured. These files are entered on the Special Files tab:

Running a Script After Installation

A post-install script can be triggered at the end of installation. This might be a background PHP script or the main web page that you want the user to see after installation, for example to guide the user through setup of the application with database creation and so on. The script can be any file in the package such as a PHP script, a plain .html file or an image. To launch the script in a web browser window check the Post-install script is interactive option. Otherwise leave this unchecked to execute the script silently. If a non-interactive post-install script does produce output such as error messages, the output will be shown in a dialog and not lost.

Configuration Files

Any files that should be configured by the user can be entered in the list of Configuration files. If configuration files are specified, after installation the end user will be able to configure those files in a text editor window locally using a Configuration Tool. Once configured, the configuration files are automatically updated in the target installation.

If the Run post-install script after configuration step box is checked and there are configuration files, the post-install script will not be run at the end of installation. Instead the script will be executed each time the end-user clicks the Apply button of the Configuration Tool and after the configurable files have been uploaded to the server. This allows any background tasks dependent on configuration files to be run again.

When configuration files are specified, a Main page path may also be given for a script that will be launched in the user's default browser when they click the Launch button of the Configuration Tool after they have completed their configuration changes.
NOTE: the Main page path is used only when configuration files have been specified. If there are no configuration files, the Main page path is ignored and only the post install script will be run.