Earlier I switched one of the Litespeed web server virtual hosts from production mode to staging mode and after gracefully restarting rails was receiving a 503 Service Unavailable error. Initially I thought that maybe Litespeed had to be restarted completely instead of just a graceful restart but that produced the same results. Below I describe…
The below error is another error related to upgrading Redmine. I imagine part of the reason I had a lot of errors is because I hadn’t upgraded this installation of Redmine, which we really just use for development, for a long time. In fact the upgrade took this installation of Redmine from 0.8.3 to Redmine…
I ran into an issue earlier where adding a sub project to an already existing Redmine project produced an error and after a little bit of troubleshooting determined that upgrading Redmine would resolve the issue. During the upgrade process I ran into some other issues including a specific migration error using rake that is noted…
The other day I did some optimization work on a PostgreSQL database and at the end needed to create migrations so the changes I was going to make could be deployed on multiple servers. It was my first shot at migrations so I wanted to note for myself and anyone else that may find it…
A friend of mine was over tonight and we were troubleshooting a issue with SVN authentication via the Redmine project management software. Redmine is built with Ruby and on this server is running via Apache and Mongrel. I needed to set the project to run in development mode but wasn’t very familiar with the Mongrel…
Starting ruby on rails in development mode with Litespeed is easy. You need to make sure that your database.yml is configured to handle development mode as well. Follow the steps below to start Litespeed running Ruby on Rails in development mode. Please note both cofiguration settings listed in step one which include setting this to…