Small Ruby Webstack

Editor's Notes

1. 9 lines of code and it works!
2. So how much code are we talking about for Ruby and Radiant Our small server is not visible Radiant’s core => 174908 loc (usually extended with plugins and own code) Rails’s core => 131990 loc
3. Rack, This is what almost all Ruby based web frameworks build on Basically it translates http to ruby
4. Rack, This is what almost all Ruby based web frameworks build on Basically it translates http to ruby
5. Even merb Default Merb 46595 loc
6. Apache + passenger, mongrel, thin, webrick
7. But there is still an other player out there...
8. But there is still an other player out there...
9. But there is still an other player out there...
10. 6 lines of code (and a Rack compatible server) and we are off
11. This is Rails’ Rack stack Each class in use stack is called Middleware
12. This is a piece of middelware, that doesn’t do much
13. Rack::Lock executes the call in a synchronize block (Mutex) ActionController::Failsafe will render 500.html if it catches an exception Rails::Rack::Metal is basically a wrapper around middleware for ease of use in a rails app ... Your own... insert google analytic tags, filter out bad words...
14. again 6 lines of code (and a Rack compatible server) and we are off
15. Each page is defined by it’s - verb (get, post, put, delete) - URI, supporting parameters, wildcards and regex - And it should (usually) respond
16. Rendering templates - erb + haml + builder from files, inline, or defined template methods - With layout files!
17. Rendering templates - erb + haml + builder from files, inline, or defined template methods - With layout files!
18. Before Filters! Passing allows for better structured code 404’s and error handeling
19. Rack as a stack Sinatra for non-data driven apps (isdemax.be, design prototyping)