Environmental variables support for configuration files

[leikoilja]

Is your feature request related to a problem? Please describe.
I cannot set various different settings dynamically for the build process.
Example: When i set analytics settings in quartz.config.ts i do it using hardcoded host and website ID

    analytics: {
      provider: "umami",
      host: "https://umami.example.com",
      websiteId: "111111111-20ee-4edc-1111-6e4ad1a1ed62",
    },

Describe the solution you'd like
being able to add .env.local file for local development build and set environmental variables on the hosting platform (Cloudflare pages for example).
And then reference those in quartz.config.ts file as process.env.UMAMI_HOST

[saberzero1]

https://nodejs.org/en/learn/command-line/how-to-read-environment-variables-from-nodejs

Can't you just pass the environment file as parameter with --env-file?

[leikoilja]

https://nodejs.org/en/learn/command-line/how-to-read-environment-variables-from-nodejs

Can't you just pass the environment file as parameter with --env-file?
that should work, thanks for the tip!
will try and get back here in a bit.

i guess an alternative approach would be to include https://github.com/motdotla/dotenv which would abstract it for .env* files to be automatically loaded into the runtime

[aarnphm]

feel free to use that on your end. I don't think adding support to quartz makes sense.

env are somewhat hard to document over different CI setup. I think the philosophy of Quartz makes it very flexible to extend, for your own garden.

[leikoilja]

https://nodejs.org/en/learn/command-line/how-to-read-environment-variables-from-nodejs

Can't you just pass the environment file as parameter with --env-file?

just tried, that approach does not work. the way the cli helpers like npx quartz build are build - they are not passing through additional options. For env variables support to work we'd need to change BuildArgv and add the actual logic of loading that file in the runtime processes