From d2ab4c593bcca09db72cbb45da5cf8276a821cba Mon Sep 17 00:00:00 2001 From: Brian Warner Date: Tue, 26 Apr 2016 10:44:54 -0700 Subject: [PATCH] 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. --- src/allmydata/scripts/create_node.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/allmydata/scripts/create_node.py b/src/allmydata/scripts/create_node.py index 9fa6e87fb..461f03dea 100644 --- a/src/allmydata/scripts/create_node.py +++ b/src/allmydata/scripts/create_node.py @@ -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")