[patch] Fast-cgi deployment documentation should encourage users supplement it hosting providers documentation.

[Grimboy]

Problems with zombie killing policies in shared-hosting environments aren't mentioned in the documentation. Some shared-hosts (such as dreamhost) kill zombie in a cron job processes making django deployed by fastcgi on them very unstable. Luckily a few of them have process names that they don't kill. The documentation should reflect this and mention allowed process names on some large shared-hosts.

[Grimboy]

Patch adding a section explaining the problem in the documentation

[Jacob]

We can't possibly keep track of all the strange crap that shared hosting providers do, nor should we; that's a job for the host's docs.

[frankie@…]

Hmm... It seems to be a common problem. Especially looking at some of the ​thankful comments on blog posts explaining it. I understand that listing quirks isn't the documentation's responsibility. However, perhaps the documentation should encourage users to consult any documentation from their providers regarding django or fastcgi in general in addition to the official documentation. I know this may seem like common sense but I'm sure some people obviously skip it because, as an example, dreamhost's documentation spells out these problems yet many people have the problem (as shown in the linked post above).

[Grimboy]

Said note

[Jacob]

Again, telling people to read their host's documentation is unnecessary, and strikes me as patronizing.