Sinatra and SQLite3 interaction
The course contents are subject to change.
Mentors
Satish Talim , Victor Goff III, Michele Garoche and others from the RubyLearning team.
RubyLearning's IRC Channel
Mentors and students hang out at RubyLearning's IRC (irc.freenode.net) channel (# RubyLearning.org) for both technical and non-technical discussions. Everyone benefits with the active discussions on Ruby with the mentors.
Here are some details on …
…Multiverse is a series of suites, each representing a collection of dependencies. We have one for Sinatra, one for Resque and one for ActiveRecord outside of Rails. The exact versions are specified by an Envfile: suite_condition("Sinatra not compatible with 1.8.6") do RUBY_VERSION != '1.8.6' end
gemfile <<-RB gem 'sinatra', '1.3.3' gem 'rack-test', :require => 'rack/test' RB
gemfile <<-RB gem 'sinatra', …
…Rails in JS. Ember is like Rails, Backbone is like Sinatra. At some point you have to use more plugins if you start with something minimal. A lot of pain if you want to write a big app with a small framework.
Andrzej : I disagree. I would use a framework for a prototype or for a small app. Once the app grows, it has its own world. I don't want the framework to go into my way. I want to have the control over the applications. I'd use Ember for smaller apps, not for bigger …
…jQuery, Handlebars, Backbone, Underscore, Sinatra, Clojure, Java, Hadoop, Cascalog. Highlight: "You don't need a database, you need a [expletive deleted] cache" So that's what we did, we traded our database for a cache.
Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...
…easily added into any existing Rails or Sinatra application. Or, if you're starting with a Helios application, you can build a new Rails or Sinatra application on top of it. This means that you can develop your application using the tools and frameworks you love, and maintain flexibility with your architecture as your needs evolve.
Give it a try and let me know what you think!
…short SitePoint book provides readers with a fun and yet practical introduction to Sinatra, a framework that makes web development with Ruby extremely simple. It's not intended to be a completely comprehensive guide to the framework or an in-depth Ruby tutorial, but will quickly get you up to speed with Sinatra and give you the confidence to start experimenting on your own.
The book is built around a real-life example project: a content management system. It's a fun and easily …
Sinatra showed us the joy of simple. The bare essentials to start working with http requests gave us back some of the Zen of creating a codebase that did exactly what it should and nothing more. Sadly, this Zen meant reinventing wheels that Rails had already rolled.
Padrino came after both of these projects and the developers learnt from them. They re-imagined the full stack using Sinatra as a base and building from there. Sinatra++ you might think.
There's a longer write up …
What's new in Sinatra 1.4? - New features, new fun.
EditorConfig - File format and plugins to make it easier to configure multiple text editors and IDEs for the same coding style.
OverAPI.com - Massive collection of programming (and other) cheat sheets.
The State of Ruby Web Application Servers - A fine roundup hidden in a Stack Overflow answer.
Heroku.json - Create a Heroku app with addons and settings taken from a json…
Sinatra is a fantastic lightweight framework for building web services. We'll use it as the server framework for the HTTP endpoints in our Service Oriented Architecture.
Unlike Rails, Sinatra isn't all that opinionated on how you set up your application (it has a few sensible defaults ), but leaves a lot of open questions on codebase structure, how to test the application, and how to make sure the client is performing as expected.
Sinatra Web Service application structure
…Rails 2.3, Postgres, memcached, redis, resque, and for websockets Sinatra, and a few other things. The front-end is communicating with the back-end via a JSON API.
I've come to the realization that this much client-side processing and decoupling is detrimental to both the speed of development, and application performance (a ton of JavaScript has to be loaded and evaluated each time you fire up the app). It's better to let the server handle HTML rendering and minimize …