[tahoe-dev] newbie question

[Greg Troxel]

"erpo41 at gmail.com" <erpo41 at gmail.com> writes:

>> There should be a command-line version of the status page, but there
>> seems not to be.
>> I use "wget http://127.0.0.1:3456/ && more index.html" :-)
>> Seriously, am I the only one who runs nodes on computers I am not
>> sitting at?
>
> I also run tahoe at a computer I am not sitting at. There is a storage
> server on my home network responsible for running tahoe, and it listens on
> an address in my private IP range. I call up the web UI from my desktop.

I never let the tahoe  web gateway listen on other than 127.0.0.1

> When I'm away from home and want to check my node status, an ssh tunnel
> with port forwarding does the job.

Sure, I can do that too, and have.

> A CLI status checking command would be cool. However, a better solution
> would be to make tahoe so reliable and self-correcting that users don't
> ever need to check the status. (I.e. 5-second wizard-based configuration,
> automatic firewall/NAT penetration, retry everything until it succeeds or
> the world comes to an end, check and repair data automatically, etc...).

File those tickets!

But "the introducer is down" isn't self-correctable - my node is fine,
as far as I can tell, and the web page shows what's going on instantly.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120730/da90d8ad/attachment.asc>