Development
Disable deploying to your database server in Capistrano
Update: I found a better way, see below I use Capistrano to not only manage deployment tasks, but also to do lots of data management and monitoring tasks. By default Capistrano will try to deploy your code to whatever server you have set to the :db role, and will try to run the migrations there too. I don’t want to hassle with getting our full rails environment working on the db server so this was always a hassle. A temporary solution was to just set the :db role to the same server as the :app role and the migrations would [...]
Complex forms, mass assignment, and the “presenter”
I’m fed up with doing a bunch of complex model aggregation in my controllers. They are too bloated. Here’s a set of links I’m trying to make sense of as I decide what to do: http://validatable.rubyforge.org/ http://pastie.textmate.org/pastes/134685 http://blog.jayfields.com/2007/02/ruby-forwardable-addition.html http://www.brynary.com/2007/4/8/fluent-interface-for-ruby-delegation http://weblog.jamisbuck.org/2007/1/11/moving-associated-creations-to-the-model http://groups.google.com/group/rubyonrails-core/browse_thread/thread/3c61e00916c365e5?pli=1 http://ryandaigle.com/articles/2008/7/19/what-s-new-in-edge-rails-nested-models Seems like if you can avoid building an extra Presenter model and keep everything in your Rails models you’re better off, though the situation if complex enough, may dictate breaking such stuff out. Handy in either scenario is Jay Fields validatable plugin for giving you better control over validations on collections of model objects. The mass assignment stuff [...]
Categories
