staging.flaredown.com doesn't work

[benlangfeld]

Since #498 we broke staging.flaredown.com because the staging app uses free dynos and therefore is unable to issue Let's Encrypt certs for custom domains, and so cert validation fails.

In the meantime,

1. Use paid dynos in staging (maybe r4g can make this happen).
2. Use the https://flaredown-staging.webapp.herokuapp.com domain for staging. Additionally we could do a redirect at the registrar for staging.flaredown.com. @lmerriam would have to set that up I think.
3. Stop forcing TLS in staging, apply Force TLS for frontend #498 only to production.

@compwron suggests a preference for 2 and possibly 1 in the future.

This issue is just a marker in case anyone wonders what happened to staging.flaredown.com.

[lmerriam]

I am totally happy to upgrade to the $7/mo hobby dyno if that will solve this most quickly while you are all working on it this week

[benlangfeld]

@lmerriam We're able to make progress using the herokuapp.com domain. It would only be necessary to solve if someone is particularly attached to the vanity domain.

[benlangfeld]

@lmerriam So it turns out that reCAPTCHA is somewhat attached to usage of the vanity domain. I'm going to upgrade staging to hobby dynos and we can figure out the financial situation later.

[benlangfeld]

Ok, that isn't a complete solution. It's necessary to drop the current A records for staging.flaredown.com and app.flaredown.com and replace them with the following CNAMEs:

app. CNAME app.flaredown.com.herokudns.com
staging. CNAME staging.flaredown.com.herokudns.com

@lmerriam Any chance you could make that change for us?

[lmerriam]

Records updated