mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-03-25 21:17:37 +00:00
initial tahoe.cfg: explain encoding params better
Meejah pointed out that new users might think the encoding parameters are fixed, something you must pick correctly when you first set up the node, and then are never allowed to change again, which is kind of anxiety-inducing. This updates the comment to explain that the encoding is stored in each filecap, and the tahoe.cfg values are only used for newly-uploaded files.
This commit is contained in:
parent
d05da27ae8
commit
d2ab4c593b
@ -112,7 +112,10 @@ def create_node(config, out=sys.stdout, err=sys.stderr):
|
||||
c.write("#key_generator.furl =\n")
|
||||
c.write("#stats_gatherer.furl =\n")
|
||||
c.write("\n")
|
||||
c.write("# What encoding parameters should this client use for uploads?\n")
|
||||
c.write("# Encoding parameters this client will use for newly-uploaded files\n")
|
||||
c.write("# This can be changed at any time: the encoding is saved in\n")
|
||||
c.write("# each filecap, and we can download old files with any encoding\n")
|
||||
c.write("# settings\n")
|
||||
c.write("#shares.needed = 3\n")
|
||||
c.write("#shares.happy = 7\n")
|
||||
c.write("#shares.total = 10\n")
|
||||
|
Loading…
x
Reference in New Issue
Block a user