Skip to content
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

ruby framework auto detect failed on Padrino #54

Closed
dclausen opened this issue Apr 4, 2014 · 2 comments
Closed

ruby framework auto detect failed on Padrino #54

dclausen opened this issue Apr 4, 2014 · 2 comments
Assignees
Labels

Comments

@dclausen
Copy link

dclausen commented Apr 4, 2014

Ruby 2.0.0-p353
Padrino 0.11.4
Codesake-dawn 1.1.0

Just after gem install codesake-dawn, I try and start the gem for the first time:

bundle exec dawn -p .
18:41:20 [*] dawn v1.1.0 is starting up
18:41:20 [!] dawn: ruby framework auto detect failed. Please force if rails, sinatra or padrino with -r, -s or -p flags

@thesp0nge thesp0nge added the bug label Apr 7, 2014
@thesp0nge thesp0nge self-assigned this Apr 7, 2014
@thesp0nge
Copy link
Owner

This is embarrassing. I'll investigate on a padrino sample app.

@thesp0nge
Copy link
Owner

Without -p flag it works. This should be some clash in command line management

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants