Environment Variables not working for Static Site on DigitalOcean App Platform


Like the title says, it seems like the environment variables are not working for my static site on App Platform.

I’m using create-react-app to build my React project.

This is my environment variable setup inside of App Platform:

I’ve added console logs to print out process.env, this is the result: NOTE: The logs I added can be found here:

Like you can see, it doesn’t detect the environment variables specified inside of App Platform. Any idea what I’m doing wrong?

Project on GitHub: Project on DigitalOcean: DigitalOcean App Platform Spec:

name: stadro
region: ams
  - name: database
    engine: PG
    version: "12"
    size: db-s-dev-database
    num_nodes: 1
  - name: server
    http_port: 3000
    instance_count: 1
    instance_size_slug: basic-xxs
    dockerfile_path: Dockerfile.development
      - path: /api
      branch: development
      deploy_on_push: true
      repo: stadro/server
      - key: NODE_ENV
        scope: RUN_AND_BUILD_TIME
        value: development
      - key: DOMAIN
        scope: RUN_AND_BUILD_TIME
        value: ${_self.PUBLIC_URL}
      - key: POSTGRES_HOST
        scope: RUN_AND_BUILD_TIME
        value: ${database.HOSTNAME}
      - key: POSTGRES_PORT
        scope: RUN_AND_BUILD_TIME
        value: ${database.PORT}
      - key: POSTGRES_USER
        scope: RUN_AND_BUILD_TIME
        value: ${database.USERNAME}
        scope: RUN_AND_BUILD_TIME
        value: ${database.PASSWORD}
        scope: RUN_AND_BUILD_TIME
        value: ${database.DATABASE}
      - key: POSTGRES_CA_CERT
        scope: RUN_AND_BUILD_TIME
        value: ${database.CA_CERT}
  - name: web-app
    environment_slug: node-js
    build_command: yarn start:development
      - path: /
      branch: development
      deploy_on_push: true
      repo: stadro/web-app
      - key: NODE_ENV
        scope: BUILD_TIME
        value: development
      - key: SERVER_URL
        scope: BUILD_TIME
        value: ${server.PUBLIC_URL}
Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer


Static sites are served as static content from CDN so they do not have access to run time environment and only build time environment variables apply to static site components.

One way to accomplish this is to generate a configuration file that you can read as part of the javascript (React) application, that then gets compiled into the final static content output.

For example if your static site spec has the env vars configured like you state:

      - key: NODE_ENV
        scope: BUILD_TIME
        value: development
      - key: SERVER_URL
        scope: BUILD_TIME
        value: ${server.PUBLIC_URL}

you could have a bash file like so:

#!/usr/bin/env bash
set -eE

# default for development

# set to SERVER_URL env var or default if not present

# create JSON data
json=$(cat <<-END
        "baseURL": "$api_url"

# safe it to config.json
echo "creating src/config.json"
echo "$json" > "src/config.json"

As part of the build process you would call the bash file:

build_command: "./ && yarn build"

Then in your React application you would use the config variable

import { baseURL } from './config.json'
// ...
const apiClient = axios.create({ baseURL })

Assuming that the building and bundling mechanism you use can automatically include the new file (config.json), that should allow you to call the server api. Hope this helps.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This comment has been deleted