You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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/
The text was updated successfully, but these errors were encountered: