rubyforgood / rubyforgood/Flaredown
staging.flaredown.com doesn't work
Open
Nobody has claimed this yet.
Hacktoberfest
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 21
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 16
Description
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,
- Use paid dynos in staging (maybe r4g can make this happen).
- 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.
- Stop forcing TLS in staging, apply #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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #498 and reviewing the three staging options listed here. No source files or tests are named; done means staging has a working, agreed-upon access path and the handling of staging.flaredown.com is documented or configured accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100