| | 1 | updating the Description for clarity: |
| | 2 | |
| | 3 | This ticket is about the proposal to have separate directories for holding the state/configuration of the LAFS gateway from the state/configuration of the LAFS client. In the current (Tahoe-LAFS v1.10) code, both of those things are maintained in one shared directory, called the "node directory" or "base directory". The state therein is actually non-overlapping: |
| | 4 | |
| | 5 | * things a client (i.e. the "tahoe" command-line tool) uses out of the base directory: |
| | 6 | - the {{{node.url}}} file to find out how to connect to the gateway |
| | 7 | - the {{{private/backupdb.sqlite}}} file to find out what files have already been uploaded |
| | 8 | |
| | 9 | * things a gateway uses out of the base directory: |
| | 10 | - everything else that is stored in there ''except'' for the {{{node.url}}}, and {{{private/backupdb.sqlite}}} files |
| | 11 | |
| | 12 | So the client never uses any of the files that are kept in that directory for the gateway's purposes, and the gateway never uses any of the files that are kept in that directory for the client's purposes. |
| | 13 | |
| | 14 | |
| | 15 | ---- original Description follows |
| | 16 | |
