5.1. Basic Settings
Basic IPF settings are entered on the Basic tab:
The product name and product version can be specified and appear on the user interface of the installation wizard in several places.
Choose the package is an archive option if you have a zip file or tar.gz file which should be used as the package when creating the installer. Usually it is preferable to use a tar.gz since some servers are able to upload these files in compressed form, then extract on the server, which might reduce transfer time. IPF requires the archive to be a single compressed folder (with subfolders and files), although the name of the top level folder will be replaced with the package folder name (see below).
Choose the package is an folder option if you have a folder which IPF should compress and use as the package. This option is more flexible than if a package is provided as an archive, since custom permissions can be set using the Permissions tab. On the other hand if the package is provided as an archive, the IPF build process will be faster. The name of the specified folder will be ignored, and replaced with the package folder name (see below).
Package Folder Name
Some applications require their top-level folder to have a specific name, other applications can have a user-defined top-level folder name, and some applications are designed to be located in the 'web root' of a domain. To achieve the first type of package, enter a name in the Default package folder name field, but leave the Allow end-user to edit the package folder name unchecked. Check this box on the other hand if the user should be allowed to modify the name of the top-level folder. Lastly, for applications that should be installed to the web-root, leave the default package folder name blank.
If a product will only be installed to remote servers, and never to an end-user's local machine, then the Allow installations to the end-user's local machine checkbox can be unchecked. This will remove the 'Installation Type' wizard step. This option would be useful, for example, if the creator of the package was intending to use the package to install to a handful of their own remote servers. If a product is for general release then usually this option should not be used.
In order to automatically enabled Loaders for ionCube Encoded files, check the Enable automatic Loader installation box. Checks will be performed on the end-user's server to verify whether the server is able to execute encoded files. If Loaders are not currently installed then the installer will attempt to transfer appropriate Loaders to the target server automatically. If this option is selected, the end-user will be prompted to enter the URL of the package on their web server.
Specify whether any encoded files are encoded in the newer ASCII format, or all are encoded in binary format. In the case of ASCII files, and where Loaders are installed on the target server but are not recent enough, updated Loaders will be installed.
The output file must be an filename ending in .exe, in an existing directory.