To briskly continue my regular series of cooking blog posts (previous post March 1st 2005) I present the vegetable dopiaza. I made one last night and it was yum, though I do admit to having been overly generous with all the spices - which I like but Louisa doesn’t.
-
Vegetable Dopiaza Recipe
January 31st, 2008Tags: cooking, curry, dopiaza, eating, food, recipe, spices, vegetarian -
Moo cows
January 31st, 2008Tags: cows, earth, field, green, moocows, mud, Photoblog, sky, soil
Taken back in 2005 actually, but rediscovered after showing up on my random slideshow.
-
North West Ruby User Group Talk: Building Brightbox
January 28th, 2008Tags: manchester, nwrug, rails, ruby, talkOh, btw, I’m doing a talk tomorrow at the North West Ruby User Group in Manchester about how we do the Ruby on Rails hosting at Brightbox.
I’ll be talking about SANs, Centos, Ubuntu, Xen, Apache, Lighty, NGINX, MySQL and other goodies. Heck, I might even mention Ruby, which would be nice considering it’s a Ruby user group.
My business partner Jeremy will be nattering about the business side and various other things.
Update: A couple of photos here and here.
-
Rubinius multiple instances, one process
January 15th, 2008Tags: apache, deployment, mongrel, processes, rails, rubinius, ruby, threadsRubinius has support (as of today!) for running multiple instances of it’s VM within one process, each VM on it’s own *native* thread, each VM running many ruby green threads. Each VM has it’s own heap and so each VM could load different apps that wouldn’t interfere with each other. We have plans for a mod_rubinius for apache that takes full advantage of this feature. Stay tuned ;)
- Ezra Zygmuntowi on a comment on Ruby Inside.
Very interesting stuff. Why bother making Rails thread safe when you have an awesome Ruby VM such as Rubinius. I’d like to see Mongrel (or FastCGI! Bring back FastCGI!) make use of this somehow, running multiple Rails instances itself in one process and distributing requests between them. Interested in knowing how it’d deal with memory leaks in external libraries though (like rmagick suffers from).
Still, you lose finer grained access to most of the nice UNIX process management stuff though then, like limiting memory usage with ulimits, but nobody seems to be using that for Ruby deployment anyway. It’s all fiddling around with Monit and such instead (why always with the steps backward!).
John Leach is a human being living in Leeds, UK.