If you have two o more domains (like a staging portal, or another website which is based to your actual project) you can fill the .env with your actual domain; an agnostic approach to a domain which will host your software.
Regarding to .env content instead, you can expose them – and your code do it – to public. This is necessary for Google Analytics and your guests to init the correct Analytics property.
Oh okay, what do you mean by domain agnostic?
If you have two o more domains (like a staging portal, or another website which is based to your actual project) you can fill the .env with your actual domain; an agnostic approach to a domain which will host your software.
Regarding to .env content instead, you can expose them – and your code do it – to public. This is necessary for Google Analytics and your guests to init the correct Analytics property.
More info here: nextjs.org/docs/basic-features/env...
Oh I see, but still it would be better to use env, right?
Sure :)
Cool, also removed that secret part from blog thanks :P