Opened 5 years ago

Closed 2 years ago

#1353 closed enhancement (no response)

Better Launching of Tahoe-LAFS with tahoe-lafs-controller

Reported by: lazygravy Owned by:
Priority: minor Milestone:
Component: apps/plugins Version: 0.9.14.1
Keywords: tahoe-lafs tahoe-lafs-controller Cc:
Parent Tickets: Sensitive: no

Description

Currently when you launch the tahoe-lafs-controller plugin, it is expecting to find the tahoe plugin in $CONFIG/../tahoe/tahoe-lafs-i2p/bin/tahoe.
However, when you install tahoe-lafs-i2p via KYTV's debian repo, this is not where the binary is expected.

I have attached a little shell script that should fix the issue.

Subtickets

Attachments (1)

tahoe-finder.sh (375 bytes) - added by lazygravy 5 years ago.
tahoe-finder.sh

Download all attachments as: .zip

Change History (4)

Changed 5 years ago by lazygravy

Attachment: tahoe-finder.sh added

tahoe-finder.sh

comment:1 Changed 5 years ago by str4d

Keywords: review-needed added

comment:2 Changed 4 years ago by zzz

Keywords: review-needed removed
Status: newinfoneeded_new

@OP

That's a nice little script but you haven't made a complete proposal on how to integrate this into the plugin.

Tahoe is currently started by clients.config. Do you propose to run the shell script from clients.config instead? Or replace the clients.config with starting Tahoe programmatically from TahoeLAFSController.java? But would that work on all OS platforms?

Or are you just proposing that we bundle the script and ask users to manually edit clients.config to call the script instead of tahoe directly?

A patch including updates to the index.jsp instructions page would be appreciated.

comment:3 Changed 2 years ago by zzz

Resolution: no response
Status: infoneeded_newclosed
Note: See TracTickets for help on using tickets.