[consulting] scaling sites with restricted downloads

[Laura Scott]

Hi everyone, I have a question about how you've approached larger  
site implementations....

In the past, I've typically set up any sites that want to control  
access to uploaded files with the private files setting (in admin/ 
settings), using a folder off the public html area. However, this can  
cause scaling problems. (Moshe Weitzman explains quite well here:  
http://www.tejasa.com/node/113.) For the most part, scaling up the  
server solution has addressed this adequately. But

My questions:

1) We're about to build two different music community sites that are  
going to need to start small but (obviously) be able to scale.  
Controlling access to uploaded mp3s etc. will be key aspects of this  
install. To (hopefully) reduce their server needs -- because, after  
all, they're musicians and thus aren't exactly flush -- I'm  
considering using public fileserver settings, and chmod-ing the  
folder to limit access to only via Drupal. Would that work? Are there  
limitations to this approach?

2) More generally, has anyone flipped an existing site's file system  
from private to public, or vice versa? I know this can wreak utter  
havoc, but it seems that some scrupulous editing of db data should be  
able to effect retroactive settings/locations fixes. I would love to  
hear any anecdotes in this area.

3) Same question for moving an existing site into having uploads  
managed by filemanager+attachment?

I know these could be considered support questions. I hope you don't  
mind my asking here, as I'm really looking for your experiences on this.

Thanks!

Laura


Laura Scott
President
laura at pingv.com

pingVision, LLC
4450 Arapahoe Ave, Suite 100
Boulder, CO 80303
www.pingv.com
303.415.2559


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20060330/67b710a5/attachment-0001.htm