4.1. Command-line Options
| -V | --version | Displays IPF version information. |
| -v | --verbose | Output verbose messages. |
| -h | --help | Display command-line help. |
| --config <path> | Specify an IPF .pfs script file. |
| --license-request | Generate a license request file for licensing the IPF product. |
| --ipf-license <path> | Specify the path to the IPF license file. Defaults to licdata.txt in the installation folder if not specified. |
| -o <output .exe> | This item sets the path of the Package Foundry's output file. |
| --package-name <name> | This item sets the name of the package, as used throughout the package installer. |
| --default-package-folder-name <name> | Default name for the top-level package folder after installation. This can be omitted. |
| --package-dir <path> | Either a folder or a file (see below) must be specified containing the files comprising the application to be installed. |
| --package-file <path> | If the application has already been compressed with a supported compression method as described below, the path of the archive may be specified. |
| --eval-key <name> | If you are using an evaluation copy of the IPF command-line tool, you must specify your evaluation key using this option. |
| --package-version <version> | The product version may be specified with this item. The default value is '1.0'. |
| --compression-level <level> | When using 'gzip' compression to compress a package folder a compression level may be specified from 0 to 9. Level 9 gives the best compression but is slower than level 1. Level 6 is a reasonable value. Level 0 specifies that no compression should be used. |
| --license-file <path> | If this item is used the specified file will be displayed during the installation process |
| --readme-file <path> | If this item is used the use will have the option of displaying the readme file at the end of the installation process. |
| --intro-file <path> | An introduction can be shown after the license agreement (or start page, if the license in not present). This introduction may contain installation instructions or other information. Either the path of a file can specified, or a URL. |
| --intro-file-external | If this option is set, the intro file will be launched externally using the Windows file association. For example, an html file will be launched in the default web browser. If this option is not set then the intro file will be displayed in the installer itself. |
| --use-default-permissions | Specifies that files and folders should be set to the permissions specified by the options --default-file-mode and --default-folder-mode instead of given the default file and folder permissions assigned by the server. This will slow down package installation as a chmod command must be issued for each uploaded file and would rarely be required. In a configuration file, use the item use-server-permissions 0 to enable this functionality. |
| --default-file-mode <mode> | When compressing a package archive with gzip compression this setting specifies the default permission mode to use for those files not specified with chmod-package. This option only applies to the Windows version of IPF, as on Linux permissions can be easily set for the package folder using the shell. The default value is 644. |
| --default-folder-mode <mode> | When compressing a package archive with gzip compression this setting specifies the default permission mode to use for those folders not specified with chmod-package. This option only applies to the Windows version of IPF, as on Linux permissions can be easily set for the package folder using the shell. The default value is 755. |
| --disable-permissions-warning | The setting of permissions will only work if the chmod command is supported on the target FTP server. If disable-permission-warning is not set, then a warning will be displayed if permissions cannot be set. The files and permissions specified with chmod-package will be listed. The warning is only displayed if at least one item is specified with chmod-package. |
| --disable-local-installs | If a product will only be installed to remote servers, and never to an end-user's local machine, then this option can be used to 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. |
| --allow-pfn-edit | When this option is set to 1 the end-user will be able to edit the package folder name. |
| --hide-product-info | When this option is set to 1 the product name and version will not be displayed over the side panel image. |
| --main-page <path> | This item can be set to the main page of the package. The Configuration Tool will then launch this page in the user's default browser when they click Launch. |
| --image-side-panel <path> | This item enables customisation of the side panel image on the first page and last pages of the package installer. The image must have file extension .png, .jpeg, .jpg, .bmp, or .gif, and be a valid image of the corresponding image format. |
| --image-motif <path> | This item enables customizations of the image appearing on the top right of most pages in the package installer wizard. As with the side panel image, this image must be in Portable Network Graphics format. |
| --disable-auto-loader-install | By default, Loaders will be installed automatically if they are not already installed on the target server. Use this option to control whether to enable the automatic installation of Loaders. |
| --all-encoded-file-binary | Use this option to specify whether all files in the application which are encoded with the ionCube Encoder have been encoded in binary mode. |
| --install-script-url <path> | Set this item to the URL of a page that should be launched in the user's default web browser after installation is complete. The URL is relative to the folder the user uploads the application into. |
| --install-script-interactive | This item specifies whether the post-install script requires user-interaction. If so, then the page will be launched in a browser, otherwise it will be executed silently by the Package Installer. |
| --run-post-install config | Sometimes a post-install script should be run at the end of the installation wizard, and sometimes it should be run after configuration files have been saved to the server. Use the value 'config' to specify that the post-install script should run after configuration, and any other value to specify that it should run after file upload and any Loader installation. |
| --stub-version <version> | Use this option to customise the version number of the installer executable file. |
| --stub-product <product name> | Use this option to customise the product name in the installer executable file's version info resource. |
| --stub-copyright <copyright> | Use this option to customise the copyright message in the installer executable file's version info resource. |
| --stub-description <description> | Use this option to customise the product description in the installer executable file's version info resource. |
| --stub-comments <comments> | Use this option to customise the comments field in the installer executable file's version info resource. |
| --stub-icon <path> | Use this option to customise the application icon of the installer executable file's version info resource. |
| --with <plugin> | IPF has a modular architecture, and this option can be used to specify which installed plugins to enable. SSL support is currently implemented as a plugin, and is the only plugin available. |
| --language-pack <locale> | Language packs can be included with the installer by using this option. End-users whose system locale to an included locale will see messages displayed in their language. See the 'locale' subfolder of the IPF installation folder for the available language packs. |
| --default-language <locale> | If the end-user's current system locale is not available as an included language pack, unlocalised (English) messages will be displayed by the installer. Specify this option to use a different language pack as the default. |
| --commmon-documents <path> | If this option is used then the common documents folder will be searched for unlocalised versions of install files (readme, license etc). Otherwise IPF will search relative to the current .pfs script. |
| --localised-documents <path> | This option sets the root of the localised documents tree. Subfolders are named according to language codes (e.g. en), or language and country codes (e.g. en_GB). Localised versions of install files are then added to the appropriate language subfolder. |
| --active-help-url <URL> | This option sets the target URL for the Help button on IPF created installers. |
Copyright 2002-2006 ionCube Ltd. All rights reserved.