Configuration
The module configuration can be done via yaml
decoration either by specifying the API key directly in yaml
or by providing a path to the API key in passwords app.
The configuration on this page describes the necessary steps for the AI Accelerator module version 1.3.0 and later.
For configuration up to 1.2.0 , see Legacy configuration.
|
UI Config
config.yaml
file
/my-light-module/decorations/ai-accelerator-ui/config.yaml
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
|
required From version Defines the field types that are going to be filled out during component, variant or page generation. Default is textField, richTextField and damLinkField.
|
||||||||
|
optional From version Defines the available templates for page generation in general. Availability rules through the site definition are working independently of this configuration.
|
||||||||
|
optional From version Defines the available component templates for page generation and component generation.
|
||||||||
|
optional From version Defines the available hyper prompt reference templates. They’re used to identify which dialog should be opened.
|
||||||||
|
optional From version Defines the default extension available for the defaultExtensions: - ExpandBlockTool - ExpandTool #.... |
OpenAI Config
/my-light-module/decorations/ai-accelerator-openai/config.yaml
apiKey: $OPENAI_API_KEY
apiKey: /path/to/apikey
For more, see Passwords app.
Azure OpenAI Config
/my-light-module/decorations/ai-accelerator-azure/config.yaml
apiKey: $AZURE_OPENAI_API_KEY
apiKey: /path/to/apikey
For more, see Passwords app.
Currently only one LLM provider is possible |
Developer samples
Check out some samples here.