package.json
files if your app already uses one. You can use the one NPM uses, and Lampix will only use the fields specified above. It is important to know that the getApps()
function returns a list of all the available apps with ALL the metadata in package.json
(at least for now).config.json
contains arbitrary information, as the application demands it, whether it's a list of strings, an enormous JSON 20 levels deep or something else. For example, configurable questions for a trivia or a survey style app could belong in config.jsonschema.json
works in tandem with config.json AND my.lampix.com, as it is used to define the structure of the data in config.json and the expected types (numeric, boolean, string, lists, objects, enum values). Based on this file, my.lampix.com will generate a custom form that can be used to edit config.json without having to redeploy the app.getAppConfig()
is the method used to retrieve the data found in config.json. As is tradition, this will be an asynchronous request and the data will be available on the success function of the promise returned.