I probably should have done this sooner but I’ve finally got around to updating Bort to Rails 2.2
Here are some other changed.
Will_paginate, AASM, Rspec and Rspec-rails updated to gems
I’ve decided to remove the above plugins and unpack the most recent version into the vendor/gems directory. The main reason is its easier to keep track of which version you’re using and what needs updating. So Bort is currently rocking the most recent versions of those gems.
Exception Notifier Email Automatically Set to the Email Set in Settings.yml
This is something I thought we’d already done but alas not. Thanks to feedback on UserVoice for that one.
README Updated
The readme has been updated to let people know that they need to change the default admin password in the bort_migration along with the RESTFUL_AUTH_SITE_KEY in each of the environment files.
If you haven’t done this yet, make sure you do it yo.
Multistage Capistrano Deployment
Thanks for Phil Jeffs for fixing this one. Bort is now setup out of the box to deploy to a staging environment along with production.
Bort Sends a 404 on ActiveRecord::RecordNotFound
This is something that I normally forget to do in applications so it’s now baked into Bort. If a user requests a page and the record it’s looking for doesn’t exist, they’ll get sent to the 404 page with the correct status. If you don’t want this to happen, just remove the code from application.rb file.
Rake db:database_dump
Matt Hall has added a rake task to allow you to dump the contents of you database. Simply run rake db:database to get a dump of all the contents of your database.
Upcoming Suggested Changes
The two main upcoming changes to Bort are:
Default User Admin Panel
A lot of people seem to want this feature. We’re currently on the fence about it. Bort has tried to keep as simple as possible while keeping the features that a lot of us use. Thoughts on this would be great.
Add i18n support
Again a lot of people seem to want this but again we’re on the fence due to the reason above.
Removal of Role_requirement
I’ve noticed a lot of people on github who fork Bort seem to remove role_requirement. Also, I’ve found myself doing the same thing in favour of other options.
What do you guys think?
Suggestions? Problems?
As always, if you have any suggestions or problems then leave a message on our UserVoice and we’ll see what we can do.
(Possibly) Related Posts
If you found this post or anything else on this site of any use, then please take the time to recommend me on Working with Rails.
20 Responses to “Bort Update to Rails 2.2”
Bort: Keep it as simple as possible or do do versions including this and that. I dont like a structure with a lot of stuff I dont need. So that I have to clean it all out ..takes a lot of unessesary time.
Gruß
Werner
Oh, cool! I’ll have to update the built-in bort template for rg (http://www.github.com/jeremymcanally/rg) to match your changes.
Re: Removal of Role_requirement, I agree. Also AASM could go. I’d be nice to swap out exception notifier with hoptoad.
This is a great thing, thanks for making it happen!
Second for Hoptoad over EN — sooo…much nicer to deal with.
Agree on role_requirement removal, it’s so simplistic that it’s not very useful for anything real, and also so simple it’s trivial to add if needed.
Something wrong with rspec / rake with the newest version; if I don’t have the rspec gem installed (should not need it since those should now be included in the vendor directory), running “rake spec” or just “rake” gives me:
rake aborted!
no such file to load — spec/rake/spectask
If I *do* have it installed as a (system) gem, “rake spec” fails with:
/usr/bin/ruby18 -Ilib:test “/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb”
/usr/bin/ruby18 -Ilib:test “/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb”
/usr/bin/ruby18 -Ilib:test “/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb”
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require’: no such file to load — spec/rails (MissingSourceFile)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require’
Maybe I’m doing something wrong, but it doesn’t seem to run at least “out of the box”.
Great job!!
Congratulations
I would like default admin interface as well but I’m not sure it belongs in Bort.
I’ve been working in Typus, an admin interface for Rails. It’s really stable, flexible and powerfull. I’ll present it next week at “Conferencia Rails” in Spain. It’s available at GitHub under the MIT license, so you can use it, fork it, send proposals and whatever you want to.
http://github.com/fesplugas/typus/tree/master
Typus is currently running in a dozen or more sites and people is quite happy with it. ;)
Thanks for this update.
About Admin interface i dont think is a good idea… should stay out of bort, everyone have it’s own idea of admin interface.
Should Bort be automatically using the included gems in the vendor directory, or do I need to config / run something in order for that to happen? It doesn’t seem to be seeing them, out of the box at least.
About admin interface: mixed feelings. On one hand, Andrea is right (above) in that everyone has their own idea of what needs to go there. On the other, some basic admin functionality that could easily be expanded *would* be nice and handy.
Gah, nevermind, I was trying things out with Rails 2.1.2 (which does not work with this version of Bort, it seems).
Upgraded to the 2.2.0 release candidate and the gems in the vendor directory apparently are loaded fine, “rake spec” now passes. Whee.
Still one niggle: it seems to require the rspec gem to be installed system-wide (even though there is a copy of it in the vendor directory). If I remove rspec from the system gems, I get:
rake aborted!
no such file to load — spec/rake/spectask
if I try to run any rake task.
Re role_requirement: Why the motion to remove this? Yah, it’s totally simple to add in if you need it, but I’m wondering why you end up removing role_requirement for new projects. Is it not useful? What are you using to manage security/permissions?
Admin area and i18n would be fantastic additions. I find myself adding these into bort then all the time (ESP admin) because they are critical components that almost every site requires.
Roles are fantastic and one of the reasons i started using bort. I love but as Gabe said they would be easy to add in… just sux to have to do that!! haha :)
thanks for publishing your fantastic app.
Personally I would think some type of role-rights based interface would be more preferred than role_requirement. I personally end up using a custom role/right solution but would love to find a plugin that suited my requirements for this and having it in bort would be great. As for the admin interface, I’m all for it. Makes one less thing I have to worry about.
Great work guys! But why removing the role_requirement? Was usefull… surely for a “starter application” more useful then an admin interface xD
Thanks aniway :)
One more detail: “rake spec” fails after changing REST_AUTH_SITE_KEY (due to fixture data no longer matching, apparently).
What do I have to do after changing the site key to get the rspec test to pass again; in other words, how do I generate the proper changes to spec/fixtures/users.yml?
A rake task to upgrade the site key *and* update the fixture would of course rock, in the future :)
Hi, im using windows and tried using bort, but i have problems with the encoding. it will have errors like invalid characters?
have you encountered this type of errors?
Nice work! I think the role_requirement is necessary for most projects.
Globalize2 could be a nice addition