Application modules and configuration

An application has "modules" and "config". Modules are everything that's loaded into an application's modules database; config is everything else.

Modules are defined into the categories defined by the REST API - assets, options, services (or "resources"), and transforms. Modules can be loaded via the REST API or via mlcp - though it is preferable to load options, services, and transforms via the REST API, as the REST API will determine the URI, collections, and permissions for each module, and it's best not to duplicate that in an mlcp script.

One possible area of confusion for modules is that the REST Client API that loads options, services, and transforms has a URL pattern starting with "/v1/config". Some of the resources under this pattern are truly configuration - indexes, namespaces, and properties. But options (query), services (resources), and transforms are all code.

Config is