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 new application wizard rbricks --new sets up and configures common functionalities in a Rails app. RailsBricks should include generators for functionalities (or 'bricks') that could be optionally added at a later stage with the --add [brick-name] option. For example, adding Google Analytics to a Rails 4 app (including the turbolinks workaround) would be done like this:
rbricks -a google-analytics
Bricks being worked on are:
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.
After several busy months, I took the time to update RailsBricks. The current version is now 2.1.0. The update includes
rbricks --recreate, the option to drop, create, migrate and seed your database, now works on all Rails apps, even those not created with RailsBricks.
Thanks to everyone who commented, forked and helped me with this iteration of RailsBricks. A special thanks to Jim Meyer for creating an alternative fork of RailsBricks.
Displaying posts 1 - 5 of 17 in total