-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes on startup #85
Comments
Last working container since January. |
:-( So, looking at the commit history, that would be 7aa8ce7 Travis has passed on basically everything since then, so hopefully it's a small issue in 60af4ea or 1ed55b4 ? 60af4ea makes significant changes to the Dockerfile. It was part of pull request #58 Actually it seems the changes are reverted in later commits, so the ultimate changes merged were not that significant: https://github.com/publiclab/mapknitter-exporter-sinatra/pull/58/files So, we should be perhaps running mapknitter-exporter-sinatra/.travis.yml Lines 21 to 28 in f873043
We are requiring mapknitter-exporter-sinatra/spec/landing_spec.rb Lines 15 to 29 in f873043
Trying to boot it up in GitPod... got what you did. https://github.com/publiclab/mapknitter-exporter-sinatra/commits/main/app.rb has had 2 commits since Jan... |
whoaaaa... mapknitter-exporter-sinatra/app.rb Line 1 in f873043
I think that's a mistake -- shouldn't
Hmm, chasing that require, it went to:
@alaxalves something weird is happening here. Isn't https://github.com/publiclab/mapknitter-exporter-sinatra/commits/main/lib/export.rb I'm a little confused at why it's requiring the mapknitter-exporter-sinatra/app.rb Line 16 in 7aa8ce7
Any help appreciated, thanks @alaxalves ! |
Running the command as per Dockerfile:
ruby app.rb ....
just returns. No server is started. This is causing crash loop.
The text was updated successfully, but these errors were encountered: