6eb7ecc2d4
* Bundle the configuration necessary to run an eepsite out of the box
with Jetty - simply edit ./eepsite/docroot/index.html and give people
the key listed on the I2PTunnel configuration page, and its up.
plus minor bugfixes / refactoring / logging
20 lines
709 B
Plaintext
20 lines
709 B
Plaintext
# fire up the web console
|
|
clientApp.0.args=7657 127.0.0.1 ./webapps/
|
|
clientApp.0.main=net.i2p.router.web.RouterConsoleRunner
|
|
clientApp.0.name=webConsole
|
|
clientApp.0.onBoot=true
|
|
|
|
# start up the SAM bridge so other client apps can connect
|
|
clientApp.1.main=net.i2p.sam.SAMBridge
|
|
clientApp.1.name=SAMBridge
|
|
clientApp.1.args=sam.keys 127.0.0.1 7656 i2cp.tcp.host=localhost i2cp.tcp.port=7654
|
|
|
|
# poke the i2ptunnels defined in i2ptunnel.config
|
|
clientApp.2.main=net.i2p.i2ptunnel.TunnelControllerGroup
|
|
clientApp.2.name=Tunnels
|
|
clientApp.2.args=i2ptunnel.config
|
|
|
|
# run our own eepsite with a seperate jetty instance
|
|
clientApp.3.main=org.mortbay.jetty.Server
|
|
clientApp.3.name=eepsite
|
|
clientApp.3.args=eepsite/jetty.xml |