Observations: a few days after launch
I spent the weekend updating the database and cleaning up some visual issues. Some lessons learned:
- When redeploying - I must kill old fastcgi processes.
- I use caching for the top two levels of the website - the results are the same for every page and don’t change over time. The third level data is small and fast enough to let be. However for every cosmetic change I make, the cached pages need to be regenerated. I have placed cache pages in a separate directory for easier management, but don’t want the first user on each cached page to wait. One option is to generate them all on my staging site and then symlink. That doesn’t work because the internal links that rails generated are absolute not relative. I ended up writing a script that make requests for all the pages
- Not many have visited so far - the search engines have not indexed it yet. I am getting some traffic from The Real Book Listening Guide and got some in the last couple of days from Happycodr a website for Rails applications.
- I’ve added some more data to the site, the tables are getting quite big - I need to do some optimizing of database access.
