Deploy project

Create a recommended deployment structure and project.

Select File >> New >> Genero Files, Deploy Project.
Enter a project name and location.
Select OK.
The empty, structured, project will be active in the Projects view. The deployment structure directories are created as a recommended way to organize your project files.

Table 1. Directory structure
Files and Folders	Description	Development (under SVN)	Deploy
bin/	Binaries. Result of compiling the sources: Genero binaries: .42r, .42m, .42x, .42f, .sch Genero RW data sources: .rdd, .xsd	N	Y
src/	Application sources.	Y	N
styles/	Genero style files: .4st, 4ad, 4tb, etc.	Y	Y
config/src	.xcf or other config file containing all application configuration information	Y	N
config/gas-app/	Compiled Application Server .xcf files to deploy in the GAS app directory.	N	Y (modified on site: absolute path)
config/fgl	fglprofile files (Machine dependent for SQLLite.)	Y	Y (modified on site)
reports/	Genero Report Writer design files: .4rp	Y	Y
snippets/	GAS snippet files referenced from the .xcf or other configuration file.	Y	Y
images/	All applications resources usually in `FGLIMAGEPATH` as images and icons.	Y	Y
app.manifest	The manifest describes the content of the archive:	N Y (if this is the source of GST setup)	Y
	General information Genero version Title, description
	Declare folders/files and their roles bin/ gas-app/ files snippet files images …
	Declare the “variables” or other information that must be resolved on deployment time: Where to copy application files as bin/, styles/, reports/… (impact on $DBPATH, $FGLDBPATH, FGLRESOURCEPATH…) Where to copy config/fgl files (impact on $FGLPROFILE) Where to copy config/gas-app/ files Variables which are machine dependent and must be resolved at deployment time
	If Genero Studio reads and takes this manifest into account (it is a source rather than generated), additional information is needed: file filters: included files, excluded files in declared folders