Pronto Run-Levels

This page contains only 'ideas in progress'.

Pronto will support run-levels. Each run-level may contain any of the following (which are stored in separate directories):

lib: These files are jars the containing java code for this runlevel.
resources: These files contain the permanent data required for the execution of the code in this runlevel that are not included in the code jar files.
conf: Configuration information for the code in this runlevel. These files are generally necessary for the start-up and continuing execution of an application.
data: Persistent state generated by the code in this runlevel. These files must be maintained between executions of the application for correct operation.
tmp: Temporary state that is generated by the code in this runlevel. These files may be deleted between executions of the application.
logs: The logs generated by the code in this runlevel. These files may be deleted during execution of the application.

By default, an application deployment using Pronto will be separable into the following levels:

base: Base libraries and other files that other runlevel libraries depend upon.
dev: Device particular code and other files that specifically enable the application to execute on the device to which it has been deployed.
app: Contains the code, and other files of the application.
inst: Contains files (and possibly code) which is specific to one instance of the application on a device.

Deployments will be able to freely configure the number, names and order of runlevels for a given application.