Informations about Facebook Link Spam ("Want to see something hot?"): http://www.barklund.org/blog... - nice done. Don't click on links you don't know...
Chef is a systems integration framework, built to bring the benefits of configuration management to your entire infrastructure. With Chef, you can: * Manage your servers by writing code, not by running commands. (via Cookbooks) * Integrate tightly with your applications, databases, LDAP directories, and more. (via Libraries) * Easily configure applications that require knowledge about your entire infrastructure ("What systems are running my application?" "What is the current master database server?")
- Thomas Witt
Our Rails customers often run into memory issues. The most frequent cause these days is what we in Support dub ‘bloated mongrels.’ To be fair, bloat has absolutely nothing to do with mongrel itself, which is a solid and fine piece of work. You can run into this problem just as easily with thin, passenger, etc. Changing to a different server will not save you, as the root cause is not the server, but the code the server is running for you. A real true-blooded memory leak is rare in comparison to the occurrence of bloating Rails instances. If your mongrels (or thins, or passenger instances) are suddenly sporting 100MB or more of extra weight, look no further: we’ve got the diet plan for you!
- Thomas Witt
Simplifying your Ruby on Rails code: Presenter pattern, cells plugin | Dmytro Shteflyuk's Home - http://kpumuk.info/ruby-on...
Today we will talk about code organization in Ruby on Rails projects. As everybody knows, Ruby on Rails is a conventional framework, which means you should follow framework architects’ decisions (put your controllers inside app/controllers, move all your logic into models, etc.) But there are many open questions around those conventions. In this write-up I will try to summarize my personal experience and show how I usually solve these problems.
- Thomas Witt
The only mid-interesting insight from the Gutzeit Google Keynote: Google is using Salesforce #e12#fail (btw, he didn't even mention Wave)
Here comes Warden! Warden is a general rack authentication framework, developed by Daniel Neighman, which handles the session in a rack middleware. The main benefit from it is that you can share your authentication strategies with several apps, so if you are using Sinatra, Rails and some others middlewares at the same time, they all rely on the same rules! Devise: strategies for authentication After we fell in love with Warden and used it in some projects, we decided to create a full stack solution as Clearance, but flexible as Authlogic, on top of Warden. The solution is Devise, a Rails Engine which handles multiple roles, each one of them with different strategies. Devise currently comes with 5 strategies:
- Thomas Witt
If you care about your user’s security, and your time, it’s time you stop asking them for passwords. Storing user passwords and handling authentication offers a bunch of problems that have already been solved, and requires a lot of work to do it right. Think about it. If you’re storing user’s passwords in your database, you’ve automatically got sensitive information on your server. Maybe it’s just a College Football Pick ‘Em site, which stores nothing too important … until you store a user’s password. Let’s face it, most users don’t use a new password for every site, so if someone breaks into your server, you’re responsible if that information is lost. So, you’ve got to make sure your server’s security is up to date. Then, it’s still possible there’s a break in, or you have a malicious developer. So you have to encrypt the passwords. But not just encrypt them, because that would still be susceptible to dictionary attacks. You have to salt each password. What about brute force login
- Thomas Witt
@OliverBerger Sitze im großen Saal, komm vorbei, ich leih Dir meines