Skip to content
generated from garronej/ts-ci

⚙️ Env var in Vite at container startup

License

Notifications You must be signed in to change notification settings

garronej/vite-envs

Repository files navigation

Bundle environment variables in Vite at build time startup time!

Documentation / Starter

Motivation

In Vite, import.meta.env variables are set at build time with vite build.
However we often want to enable the person deploying the app to define those values, we don't want to re build every time we need to change a configuration.
vite-envs facilitates this by enabling to:

docker run --env FOO="xyz" my-org/my-vite-app

Then, access FOO:

  • In the TypeScript code as import.meta.env.FOO
  • In index.html, as <title>%FOO%</title>

This eliminates the need to rebuild each time you wish to change some configuration.
More importantly, it allows you to ship a customizable Docker image of your webapp!

Features

How it works

vite-envs is a Vite plugin.
When you build your app (vite build) it generate a dist/vite-envs.sh script.
When executed, this script updates the dist/index.html by injecting the environment variables defined on the host running the script.

So, to make the dynamic injection of environment variables take place, you simply need to run the vite-envs.sh script before starting your web server.
In practice, the diff that you would need to apply to your Dockerfile would look something like this:

Dockerfile

-CMD ["nginx", "-g", "daemon off;"]
+ENTRYPOINT sh -c "./vite-envs.sh && nginx -g 'daemon off;'"

Types

Unrelated to the dynamic injection of environment variables, vite-envs also brings strict typing for import.meta.env.

types-hot-reloading.webm

Demo

image

Documentation

👉vite-envs-starter👈

Usecase example

Onyxia is a Vite app distributed as a Docker image.

Sysadmins that would like to deploy Onyxia on their infrastructure can simply use the official Docker image and provide relevant environnement variable to adjust the theme/branding of the website to their usecase as documented here.

Here are two deployment example: