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
When initially spinning up the droplet, I put it on do.matplotlib.org so we could test load a bit. I also configured all web hooks using that domain.
Now that matplotlib.org is pointing to the droplets, I modified Caddy to serve the same thing from both domains so that nothing breaks. However, that's a bit redundant, and we don't really need CF to be CDN'ing things twice (though I don't expect anyone to be accessing the duplicated subdomain.)
We can update the web hooks to point to matplotlib.org easily, but I wonder if we should leave them on a separate domain still? They'd still be served by the same server, but that would silo off the paths just in case we needed them (though that's unlikely).
The text was updated successfully, but these errors were encountered:
When initially spinning up the droplet, I put it on
do.matplotlib.org
so we could test load a bit. I also configured all web hooks using that domain.Now that
matplotlib.org
is pointing to the droplets, I modified Caddy to serve the same thing from both domains so that nothing breaks. However, that's a bit redundant, and we don't really need CF to be CDN'ing things twice (though I don't expect anyone to be accessing the duplicated subdomain.)We can update the web hooks to point to
matplotlib.org
easily, but I wonder if we should leave them on a separate domain still? They'd still be served by the same server, but that would silo off the paths just in case we needed them (though that's unlikely).The text was updated successfully, but these errors were encountered: