Little Lecturefox was Dugg to Death
Today it’s a sunny morning. I woke up after a wonderful dream and had immediately two new ideas for our lecturefox project. I started the day with a fruity breakfast. After booting my computer it takes a little while to realize what had happened to our little site. While I was at sleep and dreaming lecturefox.com was dugg to death. It was an absolute surprise. It was great. It was a shock. I am awfully sorry that our server was not so amused about the great numbers of visitors. I assume it happened something like “Proxy Error - The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /.”
We get a lot of unforeseeable traffic from stumbleupon.com and the big Digg. Someone stumbled over lecturefox. Now we are getting the first comments and very friendly reviews from all over the world. Thank you, thank you, thank you! It’s so motivating. We are very happy!
Please excuse me and the server, if you’ve had a horrible first experience with the website. We upgraded our bandwidth at once. Now I hope that the site can stand the traffic.
Please take note of the fact that we are at an early working stage. lecturefox.com is in phase one of development. We will add more features and a handful of useful items. The core element is the database with links and data about university lectures. What you can see today on the site is only a part of the project. Please come back again. Then my dream will come true.

Very useful site… Congrats! I’m glad to see another great app built with Django, my favourite web framework.
I’m looking for a good Django web host and I see lecturefox is hosted by WebFaction.
According to their home page their “shared accounts have stood the test of Digg and Slashdot with no problem.” I assume you have a shared1 account with 200GB bandwidth per month so I don’t think bandwidth is a real issue. Why lecturefox was “dugg to death”? Was the problem the limit on “max total RAM used by long-running processes” (40MB for shared 1 plan)?
Thanks
The problem was that our Apache instance only had a couple of worker processes, which wasn’t enough for all the traffic. Increasing it to 40 fixed the problem.