Opened 4 years ago

Closed 4 years ago

#1599 closed enhancement (wontfix)

support i2pcontrol standalone mode

Reported by: psi Owned by:
Priority: minor Milestone: 0.9.21
Component: apps/plugins Version: 0.9.20
Keywords: i2pcontrol Cc:
Parent Tickets: Sensitive: no

Description

what would be great is if I could use i2pcontrol without needing the router console installed, effectively i2pcontrol + jetty + router.jar

Subtickets

Change History (2)

comment:1 Changed 4 years ago by zzz

<hottuna> some functionality is dependent on the routerconsole being available. not necessarily started. but probably that too.
<hottuna> the update functionality I just added for example
<hottuna> much of the update functionality is implemented in routerconsole.jar
<hottuna> and it would not function/function well without that dependency


To clarify:

  • i2pcontrol does not depend on routerconsole classes when compiled.
  • The new update function #1536 won't work if the routerconsole is not running, because the console starts the update manager. If #1536 is coded correctly, it will fail gracefully in this situation.
  • However, i2pcontrol is a plugin. All the plugin starter code is in the console, and the console starts the plugins. No plugins will run if the console is not running. This is because plugins are installed only by user action. If we don't have a UI, there's no need for plugins.

The alternative is to package i2pcontrol as a client in a jar, started by clients.config.

Note that for an even more minimal install, you'd want i2pcontrol to work without jetty, in non-HTTP mode, whatever you call that (this is what i2pd does afaik)

comment:2 Changed 4 years ago by tuna

Milestone: undecided0.9.21
Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.