As most of you know, Ubuntu 8.10 is set to be released next week.
As usual at Ubuntu upgrade time, we’re here to help with questions and issues.
Drop us a line at support@imapenguin.com anytime.
As most of you know, Ubuntu 8.10 is set to be released next week.
As usual at Ubuntu upgrade time, we’re here to help with questions and issues.
Drop us a line at support@imapenguin.com anytime.
Mongrel has served us well for the past year or so, but the simplicity of deployment in passenger along with the ever reliable apache has lured us into extensive testing. We’re getting slightly better performance numbers from passenger over mongrel with about 2/3 of the memory footprint. Please let us know at support@imapenguin.com if you see any wonkyness with any of our services. As we migrate over night.
Had this question a couple of times this week so we decided to do a quick screencast. In this setup, there are 3 SCSI drives:
sda = 20GB
sdb = 40GB
sdc = 40GB
The OS will be installed on the sda as / and the 2 40GB drives will be setup as RAID 1 and mounted as /vmware
Need help with your setup? Email us at support@imapenguin.com.
We’re still playing with the resolution settings on Vimeo, the source video will be available for download soon…

Ubuntu pushed patches for the aforementioned Ruby vulnerabilities last night. apt-get to get them in a snap. Thanks for the quick response Ubuntu team!

Nate Clark is right. The risk of the recently announced Ruby vulnerabilities may or may not be high, but let’s not take any chances.
He’s done a quick and good how to on upgrading Ubuntu servers. Check it out. Nate Rules.

Bleh, there are some nasty ruby vulnerabilities out in the wild right now. Details are here. We’ll post an update as Linux distributions get patches to let you know who needs to take action to get fixes.
We’re compiling ruby from source for the time being on production machines until updates appear.
If you need help, it’s support@imapenguin.com
There is a bug in the capistrano git bridge that’s not been patched in the stable version yet.
If you’re getting:
fatal: Could not parse object
A quick and dirty hack is to add a task that just removes your git cache for now on the deployed server with:
desc "Clear that git cache"
task :clear_git_cache do
run "rm -Rf /#{deploy_base}/#{application}/shared/cached-copy"
end
before "deploy", "clear_git_cache"
It takes about 1 second longer to do the checkout but I don’t really notice.
Sales Guy: It’s got super high performance. It’s not built on an open source Apache system or anything like that.
Me: That’s a strange pitch to a person like me. So I’ll bet my Apache system is faster, and if something is broken will be fixed overnight by any one of a few hundred people.
Sales Guy: We have a fast turnaround and our patent pending system… blah blah.
Me: Patent doesn’t equal better. Why don’t we just put my stock Apache based system next to your system and see how they do.
——-
A few days later
——-
Me: So your system only works with Windows XP clients. No Vista? No Linux? No Macs? And it’s 50% slower than my out of the box open source solution.
Sales Guy: Uhhh. Our system does work with Vista and Macs if you disable some of their security features.
Me: Please go away.
You’ve got port 3306 (MySQL) firewalled off and you want to use a MySQL GUI every once in a while (or maybe a bunch).
This is a snap with ssh.
On your local Linux/BSD/Mac/Unix machine (works in cygwin too) edit your .ssh/config file and add:
Host somemysqlserver Hostname server.mydomain.com #your mySQL server FQDN or IP User bob #replace with your valid ssh server username LocalForward *:13306 localhost:3306
Now do:
ssh -f -N somemysqlserver
You can now connect to your localhost port 13306 and it will forward to your MySQL server’s port 3306.
Plus, it’s free and probably already installed on your systems.
Need help? support@imapenguin.com
]]>
Capistrano 2.0 doesn’t work with those mongrel recipes we all have nowadays. We scratched our head at some hacks before finding a good solution via the blog world.
Thanks to Megablaix, Inc for posting this code. Works great for us, just tack it onto the end of your deploy.rb and go:
namespace :deploy do
namespace :mongrel do
[ :stop, :start, :restart ].each do |t|
desc "#{t.to_s.capitalize} the mongrel appserver"
task t, :roles => :app do
#invoke_command checks the use_sudo
#variable to determine how to run
# the mongrel_rails command
invoke_command "mongrel_rails cluster::#{t.to_s} -C #{mongrel_conf}", :via => run_method
end
end
end
desc "Custom restart task for mongrel cluster"
task :restart, :roles => :app, :except =>
{ :no_release => true } do
deploy.mongrel.restart
end
desc "Custom start task for mongrel cluster"
task :start, :roles => :app do
deploy.mongrel.start
end
desc "Custom stop task for mongrel cluster"
task :stop, :roles => :app do
deploy.mongrel.stop
end
end
]]>