Hi All, I'm kinda interested in using tahoe-lafs for creating a backup "grid" in work due the way tahoe storage servers work (I won't be able to see what is being backed up on my systems). I had a look at for some information on how to lockdown the web interface such that only allowed users/ips can access the client gateway pages, is there any way of doing this. I can only think of using a reverse proxy in apache to give me this functionality (mapping aliases with usernames to the tahoe URI's for specific users). Is there a recommended way of doing this?
Also I had a look at http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance for some ideas on how well I would think it would perform in my case. I'm intending on storing or backing up anything up to ~5million files of roughly 3tb in total size at most. Whats the largest deployment of tahoe-lafs are there any real life examples of large systems in production? For you information I intend on storing collected respondent data from a long term study on aging and obviously keeping my data safe in a secure backup would be a good thing. If it works as well as I think it might for me, I'll probably target storing MRI data as well. Thanks, Jimmy
_______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
