ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-20 13:33:09 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
ce8d40f31b
tahoe-lafs/docs/historical/configuration.rst
Zooko O'Whielacronx e5c4e83f4c reject old-style (pre-Tahoe-LAFS-v1.3) configuration files 
Check for the existence of any of them and if any are found raise exception which will abort the startup of the node.
This is a backwards-incompatible change for anyone who is still using old-style configuration files.
fixes #1385
2011-08-01 16:24:23 -07:00

3.0 KiB
Raw Blame History

Old Configuration Files

Tahoe-LAFS releases before v1.3.0 had no tahoe.cfg file, and used distinct files for each item listed below. If Tahoe-LAFS v1.9.0 or above detects the old configuration files at start up it emits a warning and aborts the start up. (This was issue ticket #1385.)

Config setting File Comment

[node]nickname [node]web.port

BASEDIR/nickname BASEDIR/webport
[node]tub.port BASEDIR/client.port (for Clients, not Introducers)

[node]tub.port [node]tub.location

BASEDIR/introducer.port BASEDIR/advertised_ip_addresses

(for Introducers, not Clients) (note that, unlike other keys, tahoe.cfg overrode this file from Tahoe-LAFS v1.3.0 up to and including Tahoe-LAFS v1.8.2)

[node]log_gatherer.furl [node]timeout.keepalive [node]timeout.disconnect [client]introducer.furl [client]helper.furl [client]key_generator.furl [client]stats_gatherer.furl

BASEDIR/log_gatherer.furl BASEDIR/keepalive_timeout BASEDIR/disconnect_timeout BASEDIR/introducer.furl BASEDIR/helper.furl BASEDIR/key_generator.furl BASEDIR/stats_gatherer.furl

(one per line)
[storage]enabled BASEDIR/no_storage (False if no_storage exists)

[storage]readonly [storage]sizelimit [storage]debug_discard

BASEDIR/readonly_storage BASEDIR/sizelimit BASEDIR/debug_discard_storage

(True if readonly_storage exists)
[helper]enabled BASEDIR/run_helper (True if run_helper exists)

Note: the functionality of [node]ssh.port and [node]ssh.authorized_keys_file were previously (before Tahoe-LAFS v1.3.0) combined, controlled by the presence of a BASEDIR/authorized_keys.SSHPORT file, in which the suffix of the filename indicated which port the ssh server should listen on, and the contents of the file provided the ssh public keys to accept. Support for these files has been removed completely. To ssh into your Tahoe-LAFS node, add [node]ssh.port and [node].ssh_authorized_keys_file statements to your tahoe.cfg.

Likewise, the functionality of [node]tub.location is a variant of the now (since Tahoe-LAFS v1.3.0) unsupported BASEDIR/advertised_ip_addresses . The old file was additive (the addresses specified in advertised_ip_addresses were used in addition to any that were automatically discovered), whereas the new tahoe.cfg directive is not (tub.location is used verbatim).