3 ms·
Thanks for asking! Are queues ready for prime-time yet? Another vote for async mailers please - also sending more than one mail at once would be nice. Sortin
by grey-area 13y ago
Thanks for asking!
Are queues ready for prime-time yet?
Another vote for async mailers please - also sending more than one mail at once would be nice.
Sorting out secret_token.rb would be good - not sure what would work, ENV variable, auto-generating a file in production if not there, but there must be a better solution which lets you work both on Heroku and let's people avoid having secrets stored in version control by default.
Also, I know this has been a really thorny issue in the past, but the thing I add first to every single app I make is authorisation and authentication. Usually I use devise and cancan, but it'd be great to just have default rails generators for this - they could be very basic, just covering the most basic use-cases, and would obviously have to be optional. Not everyone would use them, but it would at least help a lot of beginners avoid mistakes like this:
https://www.computerworld.com/s/article/9186579/Facebook_wannabe_Diaspora_hit_on_security_issues https://www.computerworld.com/s/article/9186579/Facebook_wan...
and it would also provide guidelines for people on how to approach those topics - at present they'll tend to google a solution. That would help to emphasise that you need both of these things separately, and give us a baseline from which more complex bespoke solutions could easily be built.
- steveklabnik 13y agoQueues are not ready yet, but it's something that's being worked on. Of course, async mailers are tied up in that as well. The secret_token issue is one I'm personally interested in, we've been talking about the best way to fix it. Yeah, we already have has_secure_password, which helps with authentication, but you still end up adding gems for authorization. I'll give this some thought, thanks.
- grey-area 13y agoRather than a gem for both, what I'd personally prefer is generators, because it makes all the code explicit - I always end up customising them to some extent (particularly devise, usually I use their generator then customise), and it'd be nice to expose things like the mailers that devise sets up for password reset etc (again something almost every app requires). Will be interested to see what the Rails team comes up with though.
- tibbon 13y agoI concur that something needs to happen on queues/background jobs. Right now I've always gotta go setup Resque/Redis to make basic background stuff happen and keep the app snappy. Its not a huge pain, but it seems best-practice for lots of types of tasks.