8 docs tagged with "config"

This document describes the recommended uses of config management with Genesis frameworks. Readers must have some Linux system administration experience.

The Genesis Application Platform supports the following database technology:

The JavaScript API is accessed through the methods on the root layout object and allows for saving/loading the layout state, and dynamically adding items to the layout at runtime.

Database caching on local microservices is supported out of the box. You can configure a caching layer for any Genesis module. The cache can reduce the database workload for tables that contain static data.

Your application must have a *-processes.xml file. This contains the configuration of each module in the application (Data Server, Request Server, Event Handler, etc).

This section gives an overview of server configuration items applications may need to create or override.

Every application must have a *-service-definitions.xml file. This is where you specify the ports of the various processes. These are used to communicate internally between processes.

Site specific is an area of the run directory, on a deployed application instance, where you can override the standard definitions found elsewhere in your application.