Environment variableUse
ACCEPT_EULASet to "Y" (Yes) to confirm your acceptance of the [End-User Licensing Agreement (EULA)](https://docs.embold.io/eula/). This is a mandatory setting to use the software, acknowledging that you agree to the terms and conditions outlined in the agreement.
gamma_ui_public_hostSpecifies the URL that can be accessed from the public domain. This setting is used to define the publicly accessible address for the Gamma UI, ensuring that users outside the internal network can access the application or services through this URL.
ssl_keySpecifies the file path to the private key used in SSL (Secure Sockets Layer) communication. This key is essential for encrypting and decrypting data during secure connections, ensuring data integrity and confidentiality.
ssl_certThe file path to the SSL certificate (`.cert` file) used for establishing secure, encrypted connections. This certificate is required to authenticate the server and encrypt communication.
ssl_portSpecifies the port number used for SSL (Secure Sockets Layer) communication. It defines the network port on which secure connections (using SSL/TLS) are established for encrypted data transfer
ssl_passphraseThe passphrase required to unlock and use SSL certificates that are secured with a private key. This is typically used for authenticating encrypted communications in secure connections.
ROOT_CERTS_PATHThe variable indicates the directory where the application or service running in the Docker container should look for root certificates. In this ROOT_CERTS_PATH=/opt/gamma/certs case, the path /opt/gamma/certs is inside the container.
EMB_PROXY_HOST or emb_proxy_hostThe hostname of your proxy server (e.g., proxy.example.com)
EMB_PROXY_PORT or emb_proxy_portThe port number used by the proxy server (e.g., 3128)
EMB_PROXY_USERNAME or emb_proxy_usernameThe username for proxy authentication (if required)
EMB_PROXY_PASSWORD or emb_proxy_password The password for proxy authentication (if required)
HTTP_PROXY or http_proxyThe URL of your HTTP proxy, including authentication details if necessary (e.g., http://proxy_user:password@proxy.example.com:8080).
HTTPS_PROXY or https_proxyThe URL of your HTTPS proxy, including authentication details if necessary (e.g., https://proxy_user:password@proxy.example.com:8080).
NO_PROXY or no_proxy A list of hostnames, IP addresses, or domains that should bypass the proxy. For example:
localhost,127.0.0.1,.example.com
Excluding Multiple Servers
To exclude multiple servers, use the | separator within double quotes. For example:
no_proxy="http://localhost:3000|http://3.72.41.7:3128"
EMB_SCM_TRUST_SERVER_CERTA boolean flag (true/false) that specifies whether to trust self-signed certificates in SCM (Source Control Management) systems. Enabling this option (`true`) allows connections to SCM servers with self-signed certificates, bypassing certificate validation. This is useful when working in environments with custom or non-verified certificates.
EMB_USE_NATIVE_PYPARSER

 A boolean flag (true/false) that determines whether to use the native Python parser for analyzing Python code. Enabling this option (`true`) allows the use of the native parser, which may provide better accuracy or performance for Python code analysis, depending on the implementation.
ANALYSER_XMXANALYSER_XMX specifies the maximum heap memory allocation for the Java Virtual Machine (JVM) used during remote scans in Embold.
EMB_ANALYSER_THREADSDefines the number of threads used by the analyzer during scans in Embold. Increasing the number of threads allows for parallel processing, significantly improving performance, especially when scanning large repositories.
EMB_PARSER_THREADSSpecifies the number of threads allocated for the parsing phase in Embold. This setting is crucial for improving performance during the parsing of large repositories, as it enables parallel processing of files
EMB_CHECKER_THREADSSpecifies the number of threads to be allocated for running checkers during the code analysis process.