Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The quick website launch checklist

newsletter.agiliq.com

Post reply on HN
Print view View original

11–20 of 48 posts

Re: The quick website launch checklist

#11

Post by mkr-hn »

shabda wrote: post #4
DanWaterworth wrote: post #3

> 9. Has a robots.txt > You may have a lot of things you do not want the world to know about. (Eg user uploaded media). Use robots.txt to hide them from search engines. That's not what a robots.txt file is for. It doesn't hide files, if anything it makes files that you don't want the world to know about easier to find.

True, what I want to say is. If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth). I should probably re-word that line, but I dont want to get too technical.

If the images are relevant then you're tossing earned SE traffic and extra value in the other ranking signals Google uses. If you have 1000 posts on gardening and an image for each with gardening in the filename, you're going to have an easier time ranking for gardening.

Re: The quick website launch checklist

#12

Post by rawsyntax »

wisty wrote: post #7
robin_reala wrote: post #6

pingdom store passwords in plaintext: http://news.ycombinator.com/item?id=2865206

That's ugly. But who cares? A sophisticated user (read, anyone using Pingdom) won't be using the same password for their Pingdom account and their email. Though the consequences if they did would be ugly.

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

Re: The quick website launch checklist

#13

Post by tingletech »

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.

Re: The quick website launch checklist

#14

Post by tl »

tingletech wrote: post #13

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.

We solve this by having the e-mails come out in hourly batches for errors, with a separate, single, immediate e-mail for "the site is down" type problems.

Re: The quick website launch checklist

#18

Post by troels »

tingletech wrote: post #13

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.
Post reply on HN