Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] use runtime config #17

Open
Hulkmaster opened this issue Jan 13, 2021 · 2 comments
Open

[FEAT] use runtime config #17

Hulkmaster opened this issue Jan 13, 2021 · 2 comments

Comments

@Hulkmaster
Copy link

Problem:
in our project we build nuxt in docker image, and we matomo vars in .env
because of our architecture we cannot provide .env during build time, and thus we have to do hack specially for that plugin

Solution:
Would be nice, if that plugin would use nuxt runtime config https://nuxtjs.org/docs/2.x/configuration-glossary/configuration-runtime-config/

@dhritzkiv
Copy link

dhritzkiv commented Apr 8, 2021

Yes, supporting runtime config would be nice. Here's the documentation for how @nuxt/sentry allows configuring it

An alternative would be to do what other modules which is to allow not specifying siteId in the configuration object, and instead falling back to a pre-specified process.env value read at runtime (i.e. is not baked in by nuxt/webpack). Something like process.env.MATOMO_SITE_ID. This is how @nuxt/sentry does it too

@gb-bluspark
Copy link

gb-bluspark commented Jun 12, 2024

This fork does exactly that: https://github.com/zecar/nuxt-matomo 🔥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants