The Roadmap describes the upcoming features in RailsBricks that are currently worked on. If you have any suggestion or would like to participate, get in touch!
The work on RailsBricks 3 is already well advanced. As of now, RailsBricks 2.x won't receive any more updates and will be retired when version 3 gets released.
The goal for RailsBricks 3 is to provide more features while being easier to use. The code is not based on RailsBricks 2 but a complete rewrite. The following features are being worked on:
If you have a feature request, now is the time to send it!
The work on RailsBricks 3 has started and is already well advanced. Currently in alpha, version 3 will be released before September ends.
As of now, RailsBricks 2.x won't receive updates anymore. Version 2.3.0 released today was the last one.
As soon as RailsBricks 3 hits the stage where it is publicly released, version 2 will be retired completely. The RailsBricks Github repository will host RailsBricks 3.
RailsBricks was initially created to make my life easier. Over time, it became a popular tool to quickly generate a Rails application and automatically set up some basic functionalities like creating a user admin section.
Unfortunately, even though RailsBricks 2 is fully functional and serves its purpose well, the code has become bloated. This is mostly due to a lack of time on my part. Therefore, I started working on RailsBricks 3 with two things in mind:
This will also serve to encourage more developers to contribute code to the project.
Also, with more experience building apps with RailsBricks, I notice some missing features that would fit perfectly with the vision I have of what RailsBricks should be. One of them is a better handling of production configuration.
I got many feature requests as well. Offering a choice for a database engine, for example. This will be added to RailsBricks 3. Some feature requests such as a different templating engine won't be considered, though. I don't plan for RailsBricks to be everything to everyone.
RailsBricks 3 will have several new features. Among them are:
Some features will also be removed. Among them, the RSpec & Capybara test frameworks. Much of the feedback I get concerns changes and tweaks to adapt to the individual way developers are implementing TDD/BDD. There are simply too many options to make the right choice so I decided to remove it completely. You will be able to add the testing suite of your choice yourself after your app is generated by RailsBricks.
While I'm cooking RailsBricks 3, you are welcome to submit your feedback, suggestions and feature requests. I don't promise each feature will be implemented or even considered but I will read them carefully nonetheless.
Keep an eye on Twitter as this is where I'll announce the release of RailsBricks 3.
RailsBricks now builds apps using Rails 4.1.6. This release also includes:
If RailsBricks was made by Apple, they'd say that this is the best RailsBricks ever made!
Version 2.2.1 has been released and RailsBricks now uses Rails 4.1.5.
This new RailsBricks update is brought to you by David Hsu. Now, when selecting Devise authentication in the wizard, you have the option to choose if you want your user model to be composed of
password - Devise (login with email) - or simply
password - Devise (login with username).
RailsBricks 2.1.2 has been published with a new option to the
rbricks -b (or
rbricks --bundle) which is just a simple shortcut for
bundle install --without production --path vendor/bundle.
Displaying posts 1 - 5 of 19 in total