And a repository of Ubuntu Hardy Heron debs for mod_rails/Phusion passenger. At this time I installed mod_rails via rubygems. But if the guys at brighbox make the package so it builds/installs the Apache module automatically (without human intervention and pressing Y two times) I will install that one. Much, much nicer to use with Puppet.
Today I’ve installed Phusion passenger on one of our servers. I wanted Redmine for one of our projects so this seemede a nice opportunity to install it.
Installation was a breeze. For mod_rails as well Redmine.
So I was thinking: we have mod_rails installed, we could offer some rails hosting to attract new customers.
But I see three bears on the road with using mod_rails in a shared hosting environment.
1. Same user
Every mod_rails site runs on the same user I’ve spent hours on configuring fastcgi and suexec. But now every hosting custommer’s scripts run under their own user. Would be nice if mod_rails supported something like that.
2. Memory
I couldn’t find an option to limit the memory usage per mod_rails site. And I know how memory hungry rails can be
3. Aliases
Mod_rails doesn’t support host aliases. This is overcomable but feels like a hack. Wouldn’t it be nice if mod_rails supported aliases Pleeeeeeaaaaase?
Maybe I haven’t read the documentation to well and are my points useless In that case: please let me know!
There were some vulnerabilities in Ruby which are supposedly fixed in ruby 1.8.7. Because of that and because it's always nice to have the latest, I installed ruby from Ubuntu Intrepid on Hardy Herron.
And while I was doing that I also decided to install guessnet from Intrepid. So I don't have to compile guessnet anymore.
It involves two steps:
Updating you apt sources
Making sure only ruby and guessnet are going to be installed from the new sources. Not all the packages!
1. Updating your sources
Create /etc/apt/sources.list.d/intrepid.list and copy the following code into it:
I've installed puppet recently and I'm know trying to understand how it works and make use of it
If that's not difficult enough, I encountered this weird behaviour that the --noop argument didn't do anything. After an hour of searching I realized it was my own stupid fault!
I had to puppet configuration files: /etc/puppet/puppetd.conf (old way) and /etc/puppet/puppet.conf (new way). I browsed throught the source code and it looks like puppet first checks the old file, if it is found it parses that one. If it's not found, the new file is parsed. I don't know why, but if the old file is used, the --noop argument isn't parsed by puppet. So removing /etc/puppet/puppetd.conf was all I had to do. Pffff....
But why did I create the puppetd.conf file? Because I'v read the "Pulling strings with puppet"-book. And althought it's fairly new, puppet is advancing at a very high rate. So the book is becoming out-of-date already.
I've got some reasonable documentation about it, a kick-ass website (stolen from Dr. Nic's newgem) and some nice unit tests. I'm now integrating the gem in one of my own projects. If that's succesfull I'm gonna release a version 0.1. The version after 0.1 will have new features.
The website ws generated with webby. A really nice way to create static websites in ruby. Maybe I'll dedicate a post/tutorial to webby.
So please look at the website, install the gem and give me some feedback. It will be very appreciated!
I saw the MountainWest Ruby conference video: code generation: safety scissors of metaprogramming. And the speaker (Giles Bowkett) used vi from inside irb. And I've never liked Vi, but using an editor from within irb is nice! Especially if you're testing a big chunk of code.
So I began crawling the Internet for how he did this and I found the utility_belt gem. The utility belt contains the file I needed. So I installed the gem, edited my .irbrc and now I can use nano/gedit (or any other editor) from withing IRB!
And the bonus: a nice screencast that shows this feature in action. I tried to edit it with pitivi. But that really sucked. After I finally found it out how I could cut pieces I tried to save it and the whole program crashed. "apt-get remove pitivi"!
I've been using GIT now some weeks (for my ultra-secret ruby project) and I must say it's nice. Nothing more than nice. Just like svn was nice to use (compared to old-school full backups). When I first saw the GIT commands I was dazzling with confusion. But after two days you get the hang of it. I haven't done anything special like branching so I can't tell you about the advanced features. But the base is solid.
Ow, and github is really nice. I read somewhere that rubyforge now has git support too. Gonna check that out. But beating github will be difficult. Well, at least for now when Github is still free of charge!
As a "professional" webdesigner I know how much testing sucks and how it, at the same time, is one of the most important things to do (besides coding the stuff). That's why I appreciate Rails' very complete testsuite so much. And now with Rspec user stories (a nice tutorial here and here) and webrat it's getting even better!
The current version doesn't work to well with rails' script/console. It is very, very, very slow. So I keep using Yarv until this is fixed. It seems really promising though. Can't wait for Rubinius to become stable!
With my fabulous new project: mpd_radio I'm trying to everything right: tests, documentation, the whole shebang. So I was surfing tonight for some tutorials on rdoc. But I couldn't find a lot. Some useful links: