#1401 closed enhancement (wontfix)

allow environment variables to specify some options (e.g. node-directory)

Reported by: bj0 Owned by: nobody
Priority: normal Milestone: undecided
Component: code-frontend-cli Version: 1.8.2
Keywords: environment variables duplicity Cc:
Launchpad Bug:

Description (last modified by amontero)

Tahoe could use some environment variables for some of the settings that normally get passed on command line.

Specifically, specifying the --node-directory would be useful if you're doing a lot of work on a node that is not in ~/.tahoe so you don't have to include it in every command. Also, if you're trying to use the duplicity backend, which doesn't seem to let you pass options to tahoe, There is currently no way to make it work on a node that isn't in ~/.tahoe, and this should make that possible.

Related ticket: #2833

Change History (6)

comment:1 Changed at 2011-05-11T15:09:42Z by davidsarah

  • Component changed from unknown to code-frontend-cli
  • Keywords environment added; eviroment removed

comment:2 Changed at 2011-05-21T15:21:21Z by davidsarah

  • Summary changed from environment variables! to allow environment variables to specify some options (e.g. node-directory)

comment:3 Changed at 2012-03-29T20:08:08Z by davidsarah

  • Priority changed from major to normal
  • Type changed from defect to enhancement

comment:4 Changed at 2012-07-24T12:11:08Z by amontero

Linking to related ticket: 1661

comment:5 Changed at 2016-09-25T17:08:09Z by amontero

  • Description modified (diff)

Linking related ticket: #2833

comment:6 Changed at 2020-01-18T00:47:32Z by exarkun

  • Resolution set to wontfix
  • Status changed from new to closed

Nah. You can already do this:

$ TAHOE="tahoe --node-directory foo/bar"
$ $TAHOE ...
Note: See TracTickets for help on using tickets.