lbt/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

embedding guide update

Browse Source
This commit is contained in:
zzz
2019-11-27 12:39:48 +00:00
parent 98c4e9609c
commit 200a168ff7
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
i2p2www/pages/site/docs/applications/embedding.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Embedding I2P in your Application{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}November 2017{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.32{% endblock %}
{% block lastupdated %}2019-11{% endblock %}
{% block accuratefor %}0.9.44{% endblock %}
{% block content %}
<h2>{% trans %}Overview{% endtrans %}</h2>
@@ -221,17 +221,18 @@ At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.ja
You may omit the two streaming jars for a datagram-only app.
Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar.
Don't forget jbigi.jar, or a subset of it for the platforms you support, to make the crypto much faster.
We are currently building them for Java 7, as of 0.9.24. The source is mostly compatible with Java 6 if you want to do your own compile,
but we may start using Java 7 features at any time without notice.
Java 7 or higher is required to build.
If you're building Debian / Ubuntu packages, you should require the I2P package from our PPA instead of bundling it.
You almost certainly do not need susimail, susidns, the router console, and i2psnark, for example.
{%- endtrans %}</p>
<p>{% trans -%}
The following files should be included in the I2P installation directory, specified with the "i2p.dir.base" property.
Don't forget certificates/reseed and certificates/ssl, required for reseeding, and blocklist.txt for IP validation.
Don't forget the certificates/ directory, which is required for reseeding, and blocklist.txt for IP validation.
The geoip directory is optional, but recommended so the router can make decisions based on location.
If including geoip, be sure to put the file GeoLite2-Country.mmdb in that directory (gunzip it from installer/resources/GeoLite2-Country.mmdb.gz).
The hosts.txt file may be necessary, you may modify it to include any hosts your application uses.
You may add a router.config file to the base directory to override initial defaults.
Review and edit or remove the clients.config and i2ptunnel.config files.
{%- endtrans %}</p>
<p>{% trans -%}
License requirements may require you to include the LICENSES.txt file and the licenses directory.