Changes between Version 1 and Version 2 of Ticket #2144


Ignore:
Timestamp:
2013-12-28T17:48:26Z (11 years ago)
Author:
amontero
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2144 – Description

    v1 v2  
    33I was thinking in a Tahoe-LAFS grid being the storage backend for a web app served by common httpd servers, such as nginx.
    44Depending on your app requirements, you grid can range from a read-only cap webroot (that could be tamper-proof for free!) to more complex writtable grids, depending on your app.
    5 Your web server recieves a website GET and, instead of reading from a local filesystem directory, it reads from a dircap as the webroot. It could even execute scripts, creating a webroot not hackable if even the webserver is compromised. As far as the script cares, it's being run from a readonly filesystem.
     5Your web server recieves a website GET and, instead of reading from a local filesystem directory at /var/www, it reads from a dircap as the webroot. It could even execute scripts, making for a webroot dir not hackable even if the webserver is compromised. As far as the script cares, it's being run from a readonly filesystem.
    66
    7 Tahoe-LAFS would be the perfect match for distributedly hosting static sites inside anonymity networks, like Tor.
     7Tahoe-LAFS would be the perfect match for distributedly hosting static sites inside anonymity networks, like Tor. Lots of other usages might fit for web app farms, where you push code by changing the webroot caps of the currently served code to your newly and securely deployed code DIR-IMM cap. You can make them write files in a completely separate bucket-storage grid in a S3 fashion. Whatever your crazy app needs.
    88
    99To accomplish this, I've done a bit of research and nginx looks like a good fit and well documented.
    … …  
    3232Alongside: could not this help achieve WebDAV, just using nginx's out-of-the-box? #451
    3333
    34 Now it's just an idea, maybe it's doable and just needs a howto. Since I haven't found none, at least linking this issue in the UseCases page could bring interested parties on the same page.
     34Now it's just an idea, maybe it's doable and just needs a howto. Since I haven't found none, at least linking this issue in the UseCases page could bring interested parties on the same page. Opening Tahoe-LAFS usages to webops community could be a huge boost.