[kornnflake]

Before launching I do:

* Minify Html, Css, Js using the YUI Compressor

* Compress images using tinypng.org

* Run the tests I wrote during development

* Do a final stress test using blitz.io

* Generate a XML Sitemap for search engines and edit the robots.txt

* Run a spellcheck using checkdog.com

* Setup monit to make sure my app restarts after a crash ;)

Guess that's it ;) Funny side story: I launched my weekend project receiveee.com last week and failed big when moving to production. During developing I ran the app under admin, but I ofc didn't when moving to production. BUT, my app includes a smtp server which couldn't run on port 25 without admin rights. No error appeared, but not a single mail arrived. Even took me 10 minutes to find the problem :D

[msomers]

Thanks for the input! I've been debating the merits of minifying HTML, CSS, and JS. I learned about all three of those extensively by exploring others' code. Minifying breaks that. How do you address that issue?

[jameswyse]

Breaking the readability is the trade-off you have to make, though I think it's worth it for production code, it really brings the file sizes down and if you concatenate all your javascripts in to a single file you can really cut down on requests too.

If you use Google chrome you can click the '{}' icon inside the developer tools to 'pretty print' the javascript which helps a little!

There's also JavaScript Source Maps which you might want to look in to: http://www.html5rocks.com/en/tutorials/developertools/source...

[notJim]

You only minify the deployed CSS and JS, so in development, it's still perfectly readable. You shouldn't really need to read production js, usually, and when you do (for debugging issues that only happen in prod), the little brackets in Chrome that my sibling pointed out will be enough.