Live data from Hacker News

The quick website launch checklist

newsletter.agiliq.com

31–40 of 48 posts

Re: The quick website launch checklist

#31
post #29

Hmm, 13 drawn out items and none of them include a SQLi XSS or CSRF audit? Odds are there are plenty. Once your db and CEO's sexting logs end up on pastebin you'll probably be thinking that the robots.txt was pretty minor.

Regarding 2: If you haven't done proper index/join stress tests with hundreds of thousands to millions of rows of data pre-launch, then I really don't know what else to say besides you're doing it wrong. Finding out two days after launch that your schema is complete garbage or improperly indexed is an amateur move. Placing javascript (that's not a shiv or script loader) in your to try and disguise this isn't a good start.

Re: The quick website launch checklist

#34
post #29

Hmm, 13 drawn out items and none of them include a SQLi XSS or CSRF audit? Odds are there are plenty. Once your db and CEO's sexting logs end up on pastebin you'll probably be thinking that the robots.txt was pretty minor.

Regarding 2: If you haven't done proper index/join stress tests with hundreds of thousands to millions of rows of data pre-launch, then I really don't know what else to say besides you're doing it wrong. Finding out two days after launch that your schema is complete garbage or improperly indexed is an amateur move. Placing javascript (that's not a shiv or script loader) in your to try and disguise this isn't a good s…

Hmm, sorry, thought I was being funny. Didn't work out that way I guess.

Re: The quick website launch checklist

#35

I know the text says "... or equivalent software," but is there any great advantage between using Google Analytics or a hosted component on your own server? I feel it's impolite to subject your users to be tracked by Google and other huge companies just because they visited your website. Is there at least any tracking service that respects Mozilla's DNT[1]? [1]: http://dnt.mozilla.org/

Piwik [1] is a great alternative to Google Analytics. It is free, open source software, and it is typically self-hosted.

While I do not think it supports Do-Not-Track at this time, Piwik does have configuration options to respect emerging laws on data protection and user privacy.

[1] http://piwik.org/blog/2011/03/piwik-can-be-used-in-complianc...

Re: The quick website launch checklist

#36
post #18

Sending an email on an error might be a bad idea. We had this set up on a server that powers an API (along with our main site). During a network problem in the data center where the server could not get to the mysql, we had about 10,000 requests on the sever = 10,000 emails = the outlook guys having to reboot the exchange server because of some odd interaction with their spam filtering appliance.

I have a log that will mail me first time an error occurs. If it happens again, it will still be logged, but I don't get an email. Once I mark the error as resolved - if it happens again, I get an email.

Would you mind sharing how you set this up? That would actually make a great blog post.

Re: The quick website launch checklist

#38
post #30

Earlier quoted context omitted.

Generally, I use a different password for every site (using 1passwords generate feature). That helps guard against any site storing in plaintext

I don't understand how people get by without a password manager and a seperate password for every site these days.

Good memory works for me.
Post reply on HN