-
Notifications
You must be signed in to change notification settings - Fork 36
KittoDeployment
This documents explains how to deploy a Kitto application on a production system.
When deploying a Kitto application, you need to provide its Application Home directory with the executable file and the Metadata
and Resources
subdirectories.
Plus, you need to provide the System Home directory. While during development these two directories are separated, in deployment it is recommended that you merge them together, keeping the files from the Application Home rather than those from the System Home in case of duplicates. It is easy to set up an installation script to do that, for example with InnoSetup.
You might want to use a Web Server, such as Apache or nginx, as aproxy between your application and the network (in which case we recommend that you serve all static content off the Resources
subdirectory directly from the separate web server), but you are not required to do so. Your kitto application is a stand-alone web server and you don't need anything else, especially in a development/testing environment.
More details on using a Proxy with Kitto are available here.
In case your application uses one of the following tools you need to install specific software on the server:
- FOPTool: install Apache FOP 1.1
- ADOTool: install ADO provider
- PDFMerge: install Debenu quick PDF
- ReportBuilderTool: add Kitto.Ext.ReportBuilderTools, to uses of UseKitto.pas (you must have ReportBuilder)
- Kitto at a glance
- Getting started
- Setup
-
Basic concepts
- Basic Materials
- Controllers
- Features
- Kitto Enterprise
- Examples
- Developer's guide
- Library reference
- Frequently Asked Questions
- Kitto tips & tricks and how-tos
- Other information