awseward / call_status

Note who's on a call so you can avoid interrupting them.

awseward

…

call_status's Issues

TODOs

• Make ./call_status_checker output help/usage. Currently just prints nothing and exits. (see: #19)
• Consider trying caching on #17. It looks like maybe macos runner is just terribly slow... 🤔 (see: #17)
• Add a GitHub Action for building a release on tags (see: #21)

Heroku Exit

Context

---

Steps

• Move any state stores (DB/redis/what have you) to $new_host
• Move app to $new_host (#175)
• Set up a reverse proxy to forward clients from Heroku to $new_host
• Update client configs to point to $new_host (and/or handle HTTP 307 correctly)
  • ESP32 clients
  • Nim clients (#172, awseward/homebrew-tap#73)
  • hurl tests
• Goodbye, Heroku 😭

Open homebrew-tap PR from Release Workflow

Continuation of one of the items in #18

Invalid revision on heroku-built web binary

It seems like the heroku buildpack doesn't actually run inside a fit repo (probably just pulls a tarball and unpacks that), so revision is failing when web gets built there.

See:

2020-05-17T21:04:02.683861+00:00 heroku[web.1]: Restarting
2020-05-17T21:04:02.695903+00:00 heroku[web.1]: State changed from up to starting
2020-05-17T21:04:04.383037+00:00 app[web.1]: [DEBUG] version:  0.3.1
2020-05-17T21:04:04.383062+00:00 app[web.1]: [DEBUG] revision: fatal: not a git repository (or any parent up to mount point /)
2020-05-17T21:04:04.383063+00:00 app[web.1]: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
2020-05-17T21:04:04.383919+00:00 app[web.1]: [INFO] Jester is making jokes at http://0.0.0.0:25635
2020-05-17T21:04:04.383919+00:00 app[web.1]: Starting 1 threads
2020-05-17T21:04:05.073666+00:00 heroku[web.1]: State changed from starting to up

☝️ To view this, tail logs and give it a heroku config:set LOG_LEVEL=DEBUG