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
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
The text was updated successfully, but these errors were encountered:
This is to address #24.
Luckily HEROKU provides `SOURCE_VERSION` that can we can just pull this
information from.
Also included in this change is a switch from `debug` to `info` for this
information.
This is to address #24.
Luckily HEROKU provides `SOURCE_VERSION` that can we can just pull this
information from.
Also included in this change is a switch from `debug` to `info` for this
information.
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:
☝️ To view this, tail logs and give it a
heroku config:set LOG_LEVEL=DEBUG
The text was updated successfully, but these errors were encountered: