[Imported from Trac: page Tutorial, version 8]
parent
88bea2c119
commit
6a768a8183
25
Tutorial.md
25
Tutorial.md
|
@ -1,9 +1,6 @@
|
||||||
```
|
# Tutorial for Tahoe-LAFS (Draft)
|
||||||
===============================
|
|
||||||
Tutorial for Tahoe-LAFS (Draft)
|
## Hosts setup
|
||||||
===============================
|
|
||||||
```
|
|
||||||
# Hosts setup
|
|
||||||
|
|
||||||
In this tutorial we're gonna setup 3 nodes, whatever they are (Host+VM1+VM2)
|
In this tutorial we're gonna setup 3 nodes, whatever they are (Host+VM1+VM2)
|
||||||
|
|
||||||
|
@ -14,7 +11,7 @@ IPs and hosts are:
|
||||||
|
|
||||||
I'll use a self-explanatory prompt for each host.
|
I'll use a self-explanatory prompt for each host.
|
||||||
|
|
||||||
# Installation on each node
|
## Installation on each node
|
||||||
|
|
||||||
I like pypi so much I find it easier to do the download, extraction,
|
I like pypi so much I find it easier to do the download, extraction,
|
||||||
get dependencies and build using it.
|
get dependencies and build using it.
|
||||||
|
@ -47,7 +44,7 @@ allmydata-tahoe: 1.7.1, foolscap: 0.5.1, pycryptopp: 0.5.19, zfec: 1.4.7, Twiste
|
||||||
```
|
```
|
||||||
now Tahoe is installed \o/
|
now Tahoe is installed \o/
|
||||||
|
|
||||||
# Instantiate the nodes
|
## Instantiate the nodes
|
||||||
|
|
||||||
So, after reading running.html, configuration.txt and architecture.txt, we'll first
|
So, after reading running.html, configuration.txt and architecture.txt, we'll first
|
||||||
create an introducer node, that will get every other nodes to know each other. The
|
create an introducer node, that will get every other nodes to know each other. The
|
||||||
|
@ -162,7 +159,7 @@ The result would be as follows :
|
||||||
Then, you've got a working Tahoe-LAFS grid working !
|
Then, you've got a working Tahoe-LAFS grid working !
|
||||||
Is that all ? Well, no, it's time to learn how to use it.
|
Is that all ? Well, no, it's time to learn how to use it.
|
||||||
|
|
||||||
# File capabilities ?
|
## File capabilities ?
|
||||||
|
|
||||||
Now it's time for a bit of literature. File capabilities are unique "keys"
|
Now it's time for a bit of literature. File capabilities are unique "keys"
|
||||||
associated with the files. They are used internally by Tahoe-LAFS to identify
|
associated with the files. They are used internally by Tahoe-LAFS to identify
|
||||||
|
@ -182,7 +179,7 @@ for more informations, look at Capabilities section of:
|
||||||
and at this wiki page:
|
and at this wiki page:
|
||||||
<http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Capabilities>
|
<http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Capabilities>
|
||||||
|
|
||||||
# Access your shares
|
## Access your shares
|
||||||
|
|
||||||
You can store and access files on Tahoe-LAFS in many
|
You can store and access files on Tahoe-LAFS in many
|
||||||
different ways. The fastest is to either use the Web UI (WUI), or
|
different ways. The fastest is to either use the Web UI (WUI), or
|
||||||
|
@ -193,7 +190,7 @@ use the forms to add/get/remove files and directories. Just
|
||||||
always remember that once you create a directory, you need to
|
always remember that once you create a directory, you need to
|
||||||
save the directory's URI, or you won't be able to find it again.
|
save the directory's URI, or you won't be able to find it again.
|
||||||
|
|
||||||
## Using the CLI
|
### Using the CLI
|
||||||
|
|
||||||
The CLI behaves mostly like a standard shell, with all
|
The CLI behaves mostly like a standard shell, with all
|
||||||
commands prefixed by 'tahoe'.
|
commands prefixed by 'tahoe'.
|
||||||
|
@ -285,7 +282,7 @@ For example, here are some basic commands:
|
||||||
To get started please see `quickstart.html`_.
|
To get started please see `quickstart.html`_.
|
||||||
```
|
```
|
||||||
|
|
||||||
## Using the FTP interface
|
### Using the FTP interface
|
||||||
|
|
||||||
As Tahoe does not have user accounts management, to enable FTP access,
|
As Tahoe does not have user accounts management, to enable FTP access,
|
||||||
we need first to enable authentication and associate root caps to each
|
we need first to enable authentication and associate root caps to each
|
||||||
|
@ -298,7 +295,7 @@ For more informations about FTP/sFTP configuration refer to the documentation:
|
||||||
* <http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/frontends/FTP-and-SFTP.txt>
|
* <http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/frontends/FTP-and-SFTP.txt>
|
||||||
* <http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>
|
* <http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>
|
||||||
|
|
||||||
### Account file creation
|
* Account file creation
|
||||||
|
|
||||||
The password file is using a very simple format, each non blank/commented
|
The password file is using a very simple format, each non blank/commented
|
||||||
line is following this template :
|
line is following this template :
|
||||||
|
@ -381,7 +378,7 @@ Success: files copied
|
||||||
|
|
||||||
et voilà !
|
et voilà !
|
||||||
|
|
||||||
## Configure sFTP access
|
### Configure sFTP access
|
||||||
|
|
||||||
The procedure is slightly the same as for ftp access. You need to have the
|
The procedure is slightly the same as for ftp access. You need to have the
|
||||||
ftp.accounts files placed in ~/.tahoe/private/, and we'll consider you already
|
ftp.accounts files placed in ~/.tahoe/private/, and we'll consider you already
|
||||||
|
|
Loading…
Reference in a new issue