In Portland, Oregon all this weekend for RailsConf 2008, any like-minded readers interested in chatting over a beer?I gave a lightning talk on rubber today, if anyone wangts a more detailed demo, seek me out (twitter: mattconway).
I had a brief run-in with AppleScript trying to overcome an OS X terminal bug. and its not something I enjoyed. I would much rather be able to do scripts like this in a language I’m more comfortable in like ruby. I’ve known for a while that one of the enhancements in OS X Leopard is that it has native support for scripting the UI from within other scripting languages like python and ruby, however, I didn’t realize that I could drop those scripts in the user scripts folder (~/Library/Scripts) and have them available from the scripts toolbar icon. Read the rest of this entry »
We use capistrano to deploy our rails applications from a subversion repository that is accessed using svn+ssh. Recently we ran into a problem where Capistrano was unable to connect to subversion from some of the deployment hosts with an error like:
*** [err :: host.domain.com] ssh_exchange_identification: Connection closed by remote host
Since capistrano tries to fire off N svn checkouts simultaneously, it was running into a connection limit for ssh on the the subversion server. Turns out there is a MaxStartups setting for sshd_config which effectively determines how many clients can be trying to connect simultaneously. It defaults to 10, and our failures started happening when we went above 10. Changing the value to 50 on our svn/ssh server cleared up the problem.
One of the drawbacks of EC2 is that there are no static IPs to be had, so short of using an external (to ec2) solution, the only way to have redundant load balancers is to use dns round robin. If a load balancer instance goes down, we should ideally remove it from the round robin so that clients don’t continue to use the dead IP.
I’ve created yet another system for deploying rails apps to ec2 using capistrano. None of the others were doing it for me, primarily because I needed a way to deploy/configure/scale-up to multiple instances as needed.
Read the rest of this entry »