Vidalia trashes 'tor' different host config if 'vidalia.conf' not preserved in TBB update
If one configures 'tor' on a different host but uses TBB+Vidalia to monitor 'tor' and browse, forgetting to preserve the 'vidalia.conf' file when updating TBB results in Vidalia trashing the 'tor' relay configuration. Thankfully I had a backup.
Vidalia should first attempt to download the existing config when the IP of an remote system 'tor' is entered.
This is true for
tor-browser-gnu-linux-x86_64-2.3.25-13-dev-en-US
and
tor-browser-gnu-linux-x86_64-2.4.17-beta-2-dev-en-US
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information