21–30 of 33 posts
Earlier quoted context omitted.
Do you know how it compares to Geokit?
I just switched from geokit to geocoder in the app I'm building. I found geocoder to be significantly better for my purposes.
I'd be surprised if anyone that has built a few significant rails applications with devise would continue to use it. Unless you're going to have the most vanilla session/user/authentication management ever, fighting against devise gets downright nasty. Have had moderate success with https://github.com/NoamB/sorcery lately, however I'm not yet confident in calling this a solved problem. edit: Devise is great for getti…
Authentication can get downright nasty no matter which solution you use, but Devise does a lot of things well, is actively maintained, and well documented. In fact all of the gems from Jose Valim, including inherited_resources and simple_forms are such first rate plugins, it's difficult to imagine anyone throwing any of his work under the bus.
Side note: I wish the Rails team would take more of the Django approach and build some of these features into the core.
We used active_scaffold for an internal project. Its awesome to get a basic CRUD app going. https://github.com/vhochstein/active_scaffold
The only thing that holds it back is the learning curve, wich is strange, because behind it is just plain rails philosophy: controller methods + views with a tasty DSL to plug them together.
A big thanks to Volker for his huge work on pushing it to rails3 compatibility.
The current rails3 branch (Volker's) it very stable.
What remains to be done to make it even more awesome is:
* use nested_attributes_for and clean the custom nested attrs logic
* clean security layer witch at the moment uses gobals (and can only be used in shared nothing deploy)
* request local configuration copy to make it more runtimeasible, at the moment it uses a class var (global-ish) that, for some customisations, needs to be altered per request, and that again leads to only-shared-nothing-deploy
* ActiveModel API so Mongoid can join the fun too
* a child gem that bundles AS to make a fully featured admin interface, competing with rails_admin & friends.
Earlier quoted context omitted.
I just switched from geokit to geocoder in the app I'm building. I found geocoder to be significantly better for my purposes.
Can you expound upon that? What limits did you hit, how has geocoder fixed those, etc?
Geocoder's api feels a little bit more modern Geokit (rails3 vs 2). Having read the code for both, Geocoder was cleaner and would be easier to tweak if necessary.
So really it's just a preference: they do the same thing.
Overall, a good summary. > Since there is no more will_paginate in Rails 3, the only option is kaminari. This version of will_paginate seems to be fine in Rails 3: https://github.com/mislav/will_paginate/tree/v3.0.pre2 While I'm on the Rails 3 things you can find on Github topic, ActiveScaffold has a nice Rails 3 port here: https://github.com/vhochstein/active_scaffold
while will_paginate works fine on rails 3 it pollutes Array which kaminari doesn't. it's an easy switch as well (unless your doing some really custom stuff)
will_paginate may pollute Array, but it's been a great solution, that has worked for a long time. Be wary of upgrading for the sake of upgrading, especially with that kind of performance degradation.
I'd be surprised if anyone that has built a few significant rails applications with devise would continue to use it. Unless you're going to have the most vanilla session/user/authentication management ever, fighting against devise gets downright nasty. Have had moderate success with https://github.com/NoamB/sorcery lately, however I'm not yet confident in calling this a solved problem. edit: Devise is great for getti…
Sorcery looks cool. Thanks for the heads up.
I'd be surprised if anyone that has built a few significant rails applications with devise would continue to use it. Unless you're going to have the most vanilla session/user/authentication management ever, fighting against devise gets downright nasty. Have had moderate success with https://github.com/NoamB/sorcery lately, however I'm not yet confident in calling this a solved problem. edit: Devise is great for getti…
I recently started a rather large Rails project and am using Devise. Currently with authentication being pretty low on the list of things to do, it has helped get something in place rather quickly. Can you expand on the disadvantages of using Devise over time (and maybe compare it to your experiences woth Sorcery)?
If I were doing an app with standard model authentication, a Forum for example, I would use devise again in a heart-beat, but for any other project where I expect to have any slightly customized behavior at all, Ill be rolling my own.
Devise is brilliant if you want something straight-forward, but it is big, complicated (internally), and not very flexible.