On 8 Apr 2011, at 20:42, Adam Barrett wrote: > Drop box could work. Everyone shares the account, make two folders in out. > Public and Private. Then on a dedicated box run a cron to sync the two sets > of assets to their respective places on the web server. Then use the normal > simple auth script to validate and stream.
I really didn't consider the local file server side of the plan to be an issue. I was just fine with a SMB file server. My question was about the best method for restricting access to certain files once they are up on the web server. Dropbox is a great service, but I really don't think it would be a good solution for what we are doing. This solution is for the assets of several commercial websites. These are not working files. These are the final, published assets. There will be gigs worth of images, documents, and video. Having sync'd copies of all of this on each contributor's computer doesn't make any sense. And, while I believe that Dropbox does provide a public URL to items, I can't imagine that their terms of use allow for the content to be used as assets for a commercial website. And, even if they did, I can't imagine their system being optimal from financial and performance perspectives. Consider t-mobile.com… are you really suggesting that they would host all of their JPGs on Dropbox? I would have expected suggestions like A3, Akama, or Rackspace CloudFiles. _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
