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
Currently, you need to know that we limit the domains to which emails can be sent when in development and staging environments. When the receiving address is not in that domain, the to-address is forced to be ours.
We probably should show visible reminder about this on the dashboard since this doesn't affect us but can cause issues for developers that aren't from our company. The notice could be dismissible.
Why notice instead, for example, defaulting the forced address to admin_email? Because when working on a site that has been in production already, that email can be clients instead of ours.
I've also thought about detecting if we're on Dude dev or stage env, to put the email forcing on only in those situations. But haven't yet come up with a solution that would be reliable.
Currently, you need to know that we limit the domains to which emails can be sent when in development and staging environments. When the receiving address is not in that domain, the to-address is forced to be ours.
We probably should show visible reminder about this on the dashboard since this doesn't affect us but can cause issues for developers that aren't from our company. The notice could be dismissible.
Why notice instead, for example, defaulting the forced address to
admin_email
? Because when working on a site that has been in production already, that email can be clients instead of ours.I've also thought about detecting if we're on Dude dev or stage env, to put the email forcing on only in those situations. But haven't yet come up with a solution that would be reliable.
Thoughts @ronilaukkarinen @EliasKau?
The text was updated successfully, but these errors were encountered: