Note that there are some explanatory texts on larger screens.

plurals
  1. POTransitioning custom domains from Cedar stack to Bamboo stack
    primarykey
    data
    text
    <p>For an application hosted on Heroku that is still on the Bamboo stack <code>myapp.heroku.com</code>, how would you change over custom domains to point to the Cedar-compatible version <code>myapp-cedar.herokuapp.com</code> on the Cedar stack?</p> <p>Here are the conditions that need to be dealt with:</p> <ol> <li>The applications cannot be assigned the same Heroku application name even if they are using different stacks.</li> <li>Bamboo uses <code>.heroku.com</code> while Cedar uses <code>.herokuapp.com</code>.</li> <li>Bamboo uses <code>proxy.heroku.com</code> to handle routing, and the custom domain name is pointed here. Cedar wants you to point to <code>myapp-cedar.herokuapp.com</code>.</li> <li>For Heroku to know the application a custom domain is for, the application needs to be assigned the custom domain name on the Heroku side of things. (For Cedar, this needs to be done in addition to pointing to <code>myapp-cedar.herokuapp.com</code>.)</li> <li>A custom domain name can only be assigned to one application at a time whether on Bamboo or Cedar. So on the Heroku side of things, there will be only one application serving a domain name.</li> </ol> <p>I have submitted a ticket to Heroku support the other day asking if they allow by request two applications on Bamboo and Cedar to be assigned the same domain name. I doubt that they do this though.</p> <p>Considering DNS propagation time, what is the best way to switch over to the Cedar application with least user inconvenience?</p> <p>Let me know if this needs to be moved over to Server Fault.</p> <p><strong>Update:</strong></p> <p>We will follow the workaround suggested by Heroku support to use the <a href="https://devcenter.heroku.com/articles/ssl-endpoint" rel="nofollow">SSL endpoint</a>. The SSL endpoint serves HTTP too, and it seems they match based on the web request host and the custom domain assignments alone.</p> <p>So it seems that pointing the custom domains to the endpoint, reassigning the custom domains from the Bamboo application to the Cedar application after the DNS changes have propagated, and then pointing to the correct Cedar subdomain again after the switch will do the trick.</p> <p><strong>Update:</strong></p> <p>We ended up just doing a straightforward DNS update with some downtime. TTL was set quite low, so the DNS changes were expected to propagate quickly enough for most users.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload