search for: wesabe

While I''m at it, I should mention that we (www.wesabe.com) are hiring -- and we''d be especially psyched to hear from any puppeteers on this list. I''ve attached the job posting below; basically, we''re a small Ruby/Rails shop doing fun things in personal finance, we''re growing *really* fast... and we'...

...tails. Please take a look: I''d be curious to hear what folks think. This code has been managing our web servers for a while now, and has proved to be both stable and flexible -- but of course, there''s plenty of ways to improve it... (Patches are welcome!) -sq [1] http://wesabe.googlecode.com/svn/trunk/puppet/modules/apache2/trunk/ [2] http://code.google.com/p/wesabe/ [3] http://reductivelabs.com/trac/puppet/wiki/Recipes/DebianApache2Recipe [4] http://wesabe.googlecode.com/svn/trunk/puppet/modules/apache2/trunk/README

Hey all, I''ve open-sources Digg''s apache module: http://github.com/plathrop/puppet-module-apache I know this isn''t much more advanced than what I''ve seen a lot of people using. Here''s my proposition, though. Let''s get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module

Hi everyone, Recently, I''ve been reading about different deployment environments for rails and mongrel. One configuration I''ve started seeing is apache -> pen -> mongrel cluster. See http://errtheblog.com/post/35 as an example. Can someone explain to me the benefit of using Apache and Pen as opposed to either using apache as a load balancer or pen by itself?

I just tried browsing to: http://dev.rubyonrails.org/browser/trunk/actionpack/lib/action_view/helpers/asset_tag_helper.rb and got a Trac internal error. It looks to be this issue: http://trac.edgewall.org/ticket/5123 Could somebody upgrade the SilverCity package, if that is indeed the problem? Cheers, Brad --~--~---------~--~----~------------~-------~--~----~ You received this message