zzz
c65a97882e
- Quote the jetty.xml path in clients.config,
and adjust the migration function, to fix the
eepsite-won't-start bug on windows
40 lines
1.2 KiB
Plaintext
40 lines
1.2 KiB
Plaintext
# fire up the web console
|
|
clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
|
|
clientApp.0.main=net.i2p.router.web.RouterConsoleRunner
|
|
clientApp.0.name=Web console
|
|
clientApp.0.onBoot=true
|
|
clientApp.0.startOnLoad=true
|
|
|
|
# SAM bridge
|
|
clientApp.1.main=net.i2p.sam.SAMBridge
|
|
clientApp.1.name=SAM application bridge
|
|
clientApp.1.args=sam.keys 127.0.0.1 7656 i2cp.tcp.host=127.0.0.1 i2cp.tcp.port=7654
|
|
clientApp.1.startOnLoad=false
|
|
|
|
# poke the i2ptunnels defined in i2ptunnel.config
|
|
clientApp.2.main=net.i2p.i2ptunnel.TunnelControllerGroup
|
|
clientApp.2.name=Application tunnels
|
|
clientApp.2.args=i2ptunnel.config
|
|
clientApp.2.startOnLoad=true
|
|
|
|
# run our own eepsite with a seperate jetty instance
|
|
clientApp.3.main=org.mortbay.jetty.Server
|
|
clientApp.3.name=My eepsite web server
|
|
clientApp.3.args="eepsite/jetty.xml"
|
|
clientApp.3.delay=30
|
|
clientApp.3.startOnLoad=true
|
|
|
|
# load a browser pointing at the web console whenever we start up
|
|
clientApp.4.main=net.i2p.apps.systray.UrlLauncher
|
|
clientApp.4.name=Browser launch at startup
|
|
clientApp.4.args=http://127.0.0.1:7657/index.jsp
|
|
clientApp.4.delay=15
|
|
clientApp.4.startOnLoad=true
|
|
|
|
# BOB bridge
|
|
clientApp.5.args=
|
|
clientApp.5.delay=10
|
|
clientApp.5.main=net.i2p.BOB.BOB
|
|
clientApp.5.name=BOB application bridge
|
|
clientApp.5.startOnLoad=false
|