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
I assume this requires support on the API first or possibly even the underlying systems, but I thought I'd bring it up.
Adding a domain is in most cases not sufficient, you also need to deploy a routing change. About the only exception is the first default domain that you add. But we often add multiple domains at once (redirects, multilingual) and add one or multiple new domains to existing live projects. Every time you do that, it forces a redeploy. -W still does that, just in the background.
I think a --no-redeploy or similar flag would be super helpful and would reduce unnecessary downtimes/slow requests caused by extra redeploys.
The text was updated successfully, but these errors were encountered:
I assume this requires support on the API first or possibly even the underlying systems, but I thought I'd bring it up.
Adding a domain is in most cases not sufficient, you also need to deploy a routing change. About the only exception is the first default domain that you add. But we often add multiple domains at once (redirects, multilingual) and add one or multiple new domains to existing live projects. Every time you do that, it forces a redeploy. -W still does that, just in the background.
I think a --no-redeploy or similar flag would be super helpful and would reduce unnecessary downtimes/slow requests caused by extra redeploys.
The text was updated successfully, but these errors were encountered: