I know, why in the world would you want to do that?  Simple answer:  So I can have the file based caching turned on (which seems to require a web farm in the Community Edition).  So why is that desireable?  So I can run a web garden (not web farm) to avoid single process bottle necks on a single server.  I am desperately looking for a way to make the file based cache invaldiation work in dnn 5.1.x.  Anyone know of a way to fake a web farm on the latest Community Edition of DNN?  Anyone know how to turn on file based caching without the web farm?  I've got my web.config set to enable file based caching and it is the default caching provider, just doesn't turn on.  I know DNN is not designed to work with web gardens, so I am looking for a hack of sorts.  I am also very willing to pay anyone who can modify the code to turn this feature on.  

Thanks for any help you can provide.

Thanks Sebastian.  I understand it is not supported out of the box.  That is why I am looking for a 'hack'.  Someone to point in the right direction or be willing to be paid to do the work themselves.  Being an open source project, I'm sure it is not imposible and since DNN already has the file based caching provider I imagine a good deal of the work has already been done.

Anyone with ideas how to go beyond the out of the box functionality?

Thanks in advance!

Thanks Michael.  In versions of DNN prior to 5.1.x what you suggested is absolutely true. And that is exactly what I had done in the past. Now in DNN 5.1.x or newer versions if you set IsWebFarm = True in the web.config file the web farm does not turn on.  If you log in as host and look under the host settings you will see that the web farm is not turned on and the file caching is not activated.  Is there a new step to do now in the newer version?  I got to think this can be easily done, I'm just missing something.