services/Tahoe-LAFS.md
... ...
@@ -1,18 +1,20 @@
1
-# The idea
1
+# Tahoe LAFS
2
+
3
+## The idea
2 4
Tahoe-LAFS provides a distributed, reliable and crypted file system.
3 5
4
-# How?
6
+## How?
5 7
Some people runs Tahoe-LAFS nodes, providing space. With clients files can be published and received to the cloud. Everything will be encrypted on client side and keep redundant in the cloud.
6 8
7
-# Benefit
9
+## Benefit
8 10
Default you need only 3 of 10 parts of a file to reconstruct it. So a downtime of a tahoe node doesn't means data loss.
9 11
10 12
Because of the encryption an owner of a node don't know anything about the stored content.
11 13
12
-# Usage
14
+## Usage
13 15
To provide storage to the cloud you have to run a node.
14 16
15
-# Install and configuration
17
+## Install and configuration
16 18
To run a node you have to install tahoe-lafs at least in version 1.10. You can get source code from https://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.10.0.zip, if the version of the package in the distribution not at least 1.10. Then you have to extract it and install with `python2 setup.py build && sudo python2 setup.py install`.
17 19
18 20
Before the first start you have to create a node with `bin/tahoe create-node` or a client (doesn't provide storage) with `bin/tahoe create-client`. This will create the folder .tahoe in your home dir. In the file .tahoe/tahoe.cfg you have to enter on `introducer.furl` the link to our introducer node:
... ...
@@ -23,8 +25,8 @@ introducer.furl = pb://hck5ne642qn3oqd3jbeugwdu2l3pdqy6@172.22.192.65:44411/intr
23 25
24 26
With `bin/tahoe start` you start your local node.
25 27
26
-# Client
28
+## Client
27 29
You can reach the local node via web browser at [http://localhost:3456](http://localhost:3456).
28 30
29
-# Further informations
31
+## Further informations
30 32
Look at https://tahoe-lafs.org for further informations.
... ...
\ No newline at end of file