File system layout of a deployed archive

A Genero Archive contains application source files organised into subdirectories for modules, forms, etc. includes the MANIFEST and the external application configuration file. The directory structure is recreated when deployed.

Genero Archives are unpacked into a deployment directory. The deployment directory path is available and configurable in the GAS configuration files. The resource res.deployment.root points to the root directory for deployed archives. By default, it is configured with the value $(res.appdata.path)/deployment.

Each archive is unpacked into a dedicated directory under the $(res.deployment.root) directory. By default, the deployment tool will use the archive name (without the file extension) as the deployment directory. The directory name is completed with a timestamp representing the installation date.

Example

If the Genero Archive file included these files (in the same root directory):

./MANIFEST
./modules/app.42m
./modules/app.42r
./forms/app.42f
./xcf/app.xcf

The directory structure after unpacking the Genero archive would be similar to this, with the current timestamp used:

<APPDATA>/deployment/myapp-20130522-123456/MANIFEST
<APPDATA>/deployment/myapp-20130522-123456/modules/app.42m
<APPDATA>/deployment/myapp-20130522-123456/modules/app.42r
<APPDATA>/deployment/myapp-20130522-123456/forms/app.42f
<APPDATA>/deployment/myapp-20130522-123456/xcf/app.xcf