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
{{ message }}
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
Users who have the ya.js script installed have to make sure it doesn't get executed in non-prod environments. Figure out a way to make this as seamless as possible.
Some thoughts:
Use the domain attribute on the script tag to specify.
Pros:
Simple implementation on my side
Cons:
It still requires users to set that depending on their environment
The developer experience is not as smooth as I'd prefer
Set the domain attribute to the prod value always and use the HTTP request info (e.g. origin) in the events-api. Display all origins for a given domain attribute and let the user define environments. If origin and domain attribute match, we know it's production traffic. Flag every other origin as test.
Pros:
The simplest developer experience
Cons
Requires a setting in the UI and educating the users to configure environments
The text was updated successfully, but these errors were encountered:
Users who have the
ya.js
script installed have to make sure it doesn't get executed in non-prod environments. Figure out a way to make this as seamless as possible.Some thoughts:
domain
attribute on thescript
tag to specify.domain
attribute to the prod value always and use the HTTP request info (e.g. origin) in theevents-api
. Display all origins for a given domain attribute and let the user define environments. Iforigin
anddomain
attribute match, we know it's production traffic. Flag every otherorigin
as test.The text was updated successfully, but these errors were encountered: