lorj framework model

The framework is built over several pieces:

This is your main ruby code.

This object is the central system which implements controller/processes execution.

A configuration management object to serves processes on external data and adapt behaviors.

A process requires to define at least one Lorj::Data object type and data structure. This object will be mapped with data managed by the controller object.

It defines how to create, get, query, update or delete one Lorj::Data type

It defines functions to do what the requires the controller to do, like creating a server on hpcloud, or openstack, or even a container on docker.

Config object

lorj defines 2 different objects to provide configuration data management. But you can define your own config object as soon as you respect the API used by the framework.

This class implements a key/value system which can be predefined (default values) and structured. It uses at least one application file definition, an optional user config file and a runtime config.

Short summary about Config get, set and save

This object uses Lorj::Config object to add 1 additionnal level of files to get/set data.

Short summary about Account get, set and save.

Application config file : defaults.yaml

This file stored in your application directories defines 2 main sections:

This section contains a collection of key/values predefined for the application. all those key/value pairs can be redefined in the user config

This section is used to define config.yaml valid structure and data structure used by Lorj::Account

User config file : config.yaml

This section contains a collection of key/values. It redefines application data if exists.

This section contains a collection of key/values. No references from application.

License:

lorj is licensed under the Apache License, Version 2.0. See LICENSE for full license text.