Developer Environment Variables ​

In the application configuration lzc-manifest.yml, you can configure the environment for each service in services, as shown in the following example of configuring environment variables for bitnami/wordpress:5.8.2.

services:
  wordpress:
    image: bitnami/wordpress:5.8.2
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - DISABLE_FEATURE_ABC=yes

services:
  wordpress:
    image: bitnami/wordpress:5.8.2
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - DISABLE_FEATURE_ABC=yes

Runtime Environment Variable List ​

Each container will automatically inject the following environment variables in the runtime environment. Other variables need to be manually injected by developers.

Deployment Environment Variable List ​

During the deployment configuration phase (when the system parses lzc-manifest.yml), you can use the following environment variable values. Use ${ENV_NAME} in lzc-manifest.yml.

For example:

services:
  iperf:
    image: registry.lazycat.cloud/snyh1010/some_nginx:2694e91b783def0b
    command: -my-domain ${LAZYCAT_APP_DOMAIN}

services:
  iperf:
    image: registry.lazycat.cloud/snyh1010/some_nginx:2694e91b783def0b
    command: -my-domain ${LAZYCAT_APP_DOMAIN}

ps: OIDC-related environment variables are only injected when application.oidc_redirect_path exists