Rory
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Rails | 52,953 |  | 542,430 | 13,667 | 19 hours ago | 437 | September 09, 2022 | 820 | mit | Ruby |
| Ruby on Rails | ||||||||||
| Mvcmailer | 577 |  | 77 | 6 | 3 years ago | 11 | March 17, 2013 | 92 | mit | C# |
| A Mailer for ASP.Net MVC that forms the Email Body using MVC Views (Razor etc.) following Ruby on Rails ActionMailer style | ||||||||||
| Mvcli | 86 |  | 6 | 2 | 9 years ago | 16 | May 21, 2014 | 13 | mit | Ruby |
| A full-featured MVC framework for writing command line apps inspired by GLI, Rails and JSR-311 | ||||||||||
| Cs50_rails_seminar | 64 | 3 years ago | 5 | Ruby | ||||||
| Leila Hofer's Ruby on Rails Seminar for CS50 Fall 2015 | ||||||||||
| Refactoring To Rails | 51 | 3 years ago | 3 | Java | ||||||
| Example of refactoring a Spring/Hibernate application to Rails | ||||||||||
| Rails Practice | 48 | 10 months ago | 9 | |||||||
| 《Rails 实践：使用 Rails 4 构建在线网店》 | ||||||||||
| Code4startup.hero.new | 47 | 8 years ago | Ruby | |||||||
| Aspnetmvcturbolinks | 44 | 3 | 10 years ago | 4 | August 20, 2013 | mit | JavaScript | |||
| Rails Turbolinks integration in ASP.NET MVC | ||||||||||
| Gonrails | 37 | 2 years ago | 8 | November 02, 2020 | 1 | mit | Go | |||
| Rails like mvc backend application with golang . | ||||||||||
| Pw Mvc Boilerplate | 35 | 3 years ago | 1 | PHP | ||||||
| A Rails-inspired [something]VC boilerplate for new ProcessWire projects | ||||||||||
rory
A lightweight, opinionated framework with Rails-like conventions.
Introduction
Rory is an MVC framework for Ruby. Its conventions are very similar to that of Ruby on Rails, but fewer.
Rory was started as a self-educational project, but has evolved to the point where it is used in production environments. Its design goals, therefore, are a moving target, but are gradually moving from "understanding the design and implementation of Rails" to "creating a lightweight, opinionated framework with Rails-like conventions."
History
In 2008, I was first introduced to Ruby on Rails. I'd been an independent contract PHP developer for over 8 years, and I'd never used an MVC framework before, so I was thirsty for something different.
I loved Ruby (mostly). And Rails was great for scaffolding - getting a functional web application running quickly. However, all its "magic" (to enable convention over configuration) made it very difficult for a newcomer to understand what was going on, and to actually learn Ruby.
I griped and griped about the complexity of Rails, and about the arcane maneuvers necessary to code "outside the box," until finally I decided to take a more empathic approach, and ask the question: Why is Rails the way it is?
I figured the best way to tackle the question was to start over from scratch. Start with a specification for a web application, and nothing but the Rack gem. And thus was born Rory.
Contributing to rory
- Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
- Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
- Fork the project.
- Start a feature/bugfix branch.
- Commit and push until you are happy with your contribution.
- Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
- Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
Copyright
Copyright (c) 2013 Ravi Gadad. See LICENSE.txt for further details.
