Configuration
Appmixer Engine
APP_NAME
The authentication popup windows do contain the Appmixer title by default. If you want to change that, set the APP_NAME env variable in the Appmixer engine.
![](https://docs.appmixer.com/~gitbook/image?url=https%3A%2F%2F4257661311-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FkpyTqJi517UiwFJJRydZ%252Fuploads%252Fgit-blob-54d2307486c62b39f9b4d3a7c406df2e99325ea8%252FACME_and_Appmixer.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ef07151e&sv=1)
Example from the docker-compose.yml
LOG_LEVEL
By default set to info
. Can be changed to error
, warn
or debug
.
LOG_COMPONENT_DATA_MESSAGE
When set to false
, the component's input/output messages won't be logged into Elasticsearch.
Important! Appmixer Insights and Designer log messages won't contain any items if logging data messages are turned off.
APPMIXER_HTTPS_PROXY and APPMIXER_HTTP_PROXY
Set up a proxy using these ENV variables. All HTTP(S) requests from Appmixer will be redirected to the proxy URL.
Token encryption
Most of the connectors in Appmixer require user authentication. That can be represented as OAuth access tokens, API keys, or username/password combinations.
If you want (and you should) to enable token encryption, set the ENCRYPTION_ENABLED environment variable to true
. Then you have to set the ENCRYPTION_SECRET environment variable. These variables cannot be set through the Backoffice.
If you lose the encryption secret, you will not be able to recover the encrypted tokens.
Last updated