web.port can conflict

[joeyh]

I created 2 separate tahoe nodes on my laptop, and got some very surprising behavior. It turned out that tahoe create-node puts in a default web.port, and if 2 nodes have the same port, any tahoe command will assume that, since it connects to the configured port, it's talking with the right node.

This impacts at least the git-annex tahoe special remote, which sets up a tahoe node for the user. Users sometimes have more than 1 git-annex repository, and so will try to set up separate tahoe special remotes (which might connect back to the same grid, or not).

It would be great if web.port could be set to something like tcp:any:interface=127.0.0.1, and then tahoe start could just pick any free port.

[zooko]

Note that the node currently does this desired behavior for client.port (docs​, source​), so this ticket would be to make web.port behave similarly to client.port.

[zooko]

This is one of two issues blocking the git-annex↔LAFS integration, as mentioned here: ​http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=85272d8a988b249d755ac3f8133e2bf8126fb271 . The other is #2149.

[daira]

See also #1377: "tahoe start" claims to have started when it didn't (due to port number conflict)

[joeyh]

This is blocking adding easy point-n-click configuration of tahoe in the git-annex webapp. I could arbitraily limit it to one tahoe remote to avoid the problem, but that doesn't feel right.

[warner]

Milestone renamed

[warner]

renaming milestone

[exarkun]

Moving open issues out of closed milestones.

[meejah]

Ticket retargeted after milestone closed