GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
I feel that any code included in config.ru should be ran when running the app in development mode.
Mmm, I don't know about that @postmodern. The way I see it, config.ru is there for rackup to pick it up and for application servers to work properly.
What are you trying to achieve? Maybe config/boot.rb or config/apps.rb are a better fit?
I was thinking of adding middleware to config.ru so that it would run before Padrino's middleware.
What you're really looking for, I feel, is something like foreman.
Just trying to use a middleware before Padrino's own middleware, in particular Rack::Protection::AuthenticityToken.
@postmodern and why don't you just ran your app using rackup instead of padrino start? It's virtually the same thing :)
rackup doesn't do reloading, also I could see it confusing developers.
@postmodern For now, you can use Padrino.use for that, which puts things in front of the whole Padrino stack.
I do, however, get this request quite often and I think its reasonable, because it makes all environments behave the same.
@skade should we plan this for 0.12 maybe?
Not earlier, it might surprise people.
@skade can u work on this?
Merge pull request #1597 from padrino/1260-eval-config
load config.ru with padrino server, fixes #1260