I’m launching a rails website, the app is written and works, undoubtedly it’ll be an unmitigated disaster when I launch but none the less I thought I’d least attempt to give myself the best chance of success by asking all the gurus here for some advice – pre launch advice if you like. In an ideal world I’d spend days and hours on all of these things and get it absolutely spot on, but as we all know the world is not ideal and time is a precious commodity so I’m calling for comment as to which of these are most important. i.e. what should I do first and spend most time on! For context, my initial deployment will be on a shared webhost (a joyent shared accelerator). If I get a modicum of success I guess in time I’ll need to move it to a more appropriate product (read, more bandwidth, RAM capacity etc). So this is a brain dump of all the tings that I could possibly spend some time on in the coming days, to basically finish and polish the app to v1.0. I’d be really grateful for comment. Sorry for the long post, but I wanted to get few things off my chest in one go.
- clear down log files - build a rake task for backups (thinking backing up the database and any paperclipped images that users have uploaded (cron?) to a tarball nightly and FTP’ing that tarball off the webhost nightly) - build in some sort of dynamic error alerting system to email when errors occur (a la hoptoad / exception_logger / make one) - clear down as much space as possible on your webhost (breathing space / housekeeping) - clear out as much unused code as possible from the app (make it easier to maintain) - comment the app code (yes, I know, should do this while going along) - write some tests and err test (I can imagine a great number of people up in arms at this one, ok, I admit it, my app has no tests – reason is I never learned how, so I haven’t done it – would love to test and realise the importance but at the moment my testing amounts to me seeing something break in the browser and fixing it) - make sure google analystics is working (so real hits can be tracked) - include at least some metadata making a stab at initial SEO - backups - register the site with as many search engines manually as possible (e.g bing) - Performance tweaks : tweak all the active record finder methods and make sure they’re optimised, basically things like don’t find all records when you don’t need to. - Performance tweaks: optimise images in photoshop, i.e. reduce file sizes - Dump those generic error pages in /public (e.g. the 404, make something nicer, less generic rails) - git, my git workflow is simple so far, I do this on my mac “git add .” “git commit –a –m “some changes” “git push origin master”, then I ssh to my apps web directory on my host and do “git pull”, life is good. Should I just keep doing this when the app goes live, I’d like to as it works but I wonder if I should create some sort of v1.0 (is it called a branch or a tag or something), maybe I should just continue with my current workflow with a commit message like “THIS IS IT, V1.0” hehe. - *** Anything else I haven’t thought of that are real musts before going live! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
