Skip to main content

Quave ONE Environment Variables

Within your running container on Quave ONE, certain environment variables are accessible.

If additional information about your running containers is needed, feel free to contact us.

Version Information​

  • ZCLOUD_IMAGE_VERSION: This value increases by 1 for each build, represented as v1, v2, v3, and so forth.
  • ZCLOUD_DEPLOYMENT_VERSION: This increments by 1 for each new deployment. It resets to 1 for each new image.

For instance, with the first image build, you'll see: Image: v1, Deployment: v1. After a change and redeployment of the same image, it will display: Image: v1, Deployment: v2.

Building a new image will yield: Image: v2, Deployment: v1. The deployment counter resets to v1 for each new image.

Most likely, your primary concern will be ZCLOUD_IMAGE_VERSION.

Container Information​

  • HOSTNAME: This represents the full name of the container. For example, wa-app-prod-7c9bf96bcc-grbcl, where wa stands for web application, app refers to the app name (or slug) within Quave ONE, prod indicates the environment name (or slug) in Quave ONE, 7c9bf96bcc signifies the image hash, and grbcl denotes the pod name in Kubernetes.

Trusted Certificates​

  • NODE_EXTRA_CA_CERTS: Images built from a preset or a Dockerfile written in the dashboard set it to /quave-one-tls/ca.crt, the Quave One Root CA mounted in every container, so Node.js trusts managed databases and other internal services. It adds to Node's built-in roots, so public HTTPS keeps working. A value set by your Dockerfile, base image or app environment variables always wins. For a repository Dockerfile or a prebuilt image, set it yourself (see the Root CA page).