Rocky Migration
Posted by BadReligion
So the move to Typo has not gone as smooth as I'd hoped. Not to any fault of the Typo software, I feel that the issues are mostly related to typical migration from a custom built application to a prebuilt solution. Furthermore I am not turning back by any means. I know that once I get some of the details ironed out the site will get more attention and I will be much happier with it.
I need to tweak my Capistrano deployment scripts to be Typo friendly. Some confusion seems to exist when Capistrano tries to restart Typo, I have concluded that when Typo tries to stop the current running daemon it cannot find the pid.txt because it exists in the previous release which has already been unlinked. Some simple Capistrano magic will fix that.
I am also having some issues with themes. They worked fine at first but now it seems that only the default Typo theme actually installs its images and stylesheets into public. Each theme when active installs its custom images and stylesheets into public/images/theme and public/stylesheets/theme. The proper URL's are not generated either.
Lastly I have only migrated in the old blogs, I have migrated categories but none are linked up yet. I will probably migrate the comments, but since so few exist I have prioritized getting the site functioning the way I want it.
