On: Bash Pitfalls

[mlacitation]

I have a mirror of this site. wooledge.org runs off of greycat's (#bash on freenode) home DSL connection:

http://bash.cumulonim.biz/BashPitfalls.html

[Sivart13 → mlacitation]

Seriously? They can't find a better place to host a site like this here in 2013?

[clarry → Sivart13]

If you already have a machine serving stuff at home, adding a remote server is only time, money, and effort spent. Is it worth it? Not all sites are high in volume, and even well prepared sites on decent lines can go down if it hits the HN front page.

People do occasionally bitch and moan about slow downloads from my home host, but nobody ever offered money for a pain-free alternative.

[jjwiseman → clarry]

Google doc, gist, tumblr, any free blog engine.

[clarry → jjwiseman]

None of which are pain-free to me.

[Dylan16807 → clarry]

Dropbox? Unless you're pushing gigabytes per day it should make a perfect static host with urls no more ugly than previously mentioned services.

[wyclif → mlacitation]

Thanks. I don't understand why people submit links with content that can't be accessed by more than a few users simultaneously.

[jamesbritt → wyclif]

How would one know this in advance?

[wyclif → jamesbritt]

How would one know in advance that submitting to HN would result in traffic consisting of more than a handful of users?

[jamesbritt → wyclif]

How would one know in advance whether a site can handle high traffic?

And did I really have to spell this out?

[joshbaptiste → wyclif]

Well it is the main reference but it won't sustain the "HN effect", thanks for the mirror link. I typically use http://wiki.bash-hackers.org/doku.php which also provides a mirror and some extras.