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

Replace all references to eepSite with I2P Site

Browse Source
This commit is contained in:
idk
2020-11-27 16:16:49 -05:00
parent 1a39ae4cab
commit bc139e5a7c
54 changed files with 116 additions and 116 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/pages/site/misc/i2ptunnel-migration.html
View File

@@ -6,7 +6,7 @@
<p>{% trans -%}
After upgrading to the new architecture, you'll have to do a
little work to get your old I2PTunnel-driven servers running.
Lets walk through a simple example. For an I2P site with the
Lets walk through a simple example. For an I2P Site with the
old clientApp configuration, you had:
{%- endtrans %}</p>
<pre>
@@ -18,8 +18,8 @@ old clientApp configuration, you had:
<li>{% trans url='http://localhost:7657/i2ptunnel/' %}Jump to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
<li>{% trans %}Click on Add new: [Server tunnel] "GO"{% endtrans %}</li>
<li><ul>
<li>{% trans %}For the name: <code>"I2P site"</code>{% endtrans %}</li>
<li>{% trans %}For the description: <code>"My I2P site, isn't it pretty?"</code>{% endtrans %}</li>
<li>{% trans %}For the name: <code>"I2P Site"</code>{% endtrans %}</li>
<li>{% trans %}For the description: <code>"My I2P Site, isn't it pretty?"</code>{% endtrans %}</li>
<li{% trans %}>For the target host:{% endtrans %} <code>localhost</code></li>
<li>{% trans %}For the target port:{% endtrans %} <code>80</code></li>
<li>{% trans -%}

2
i2p2www/pages/site/misc/i2ptunnel-services.html
View File

@@ -2,7 +2,7 @@
{% block title %}{% trans %}I2PTunnel services{% endtrans %}{% endblock %}
{% block content %}
<p>{% trans -%}
Below is quick copy of aum's I2P site deployment guide.
Below is quick copy of aum's I2P Site deployment guide.
{%- endtrans %}</p>
<strong>{% trans %}1. - Deploy a local server{%- endtrans %}</strong>

24
i2p2www/pages/site/misc/ticket919.html
View File

@@ -11,17 +11,17 @@ with version 0.9.5. Other operating systems are not affected.
<h2>Background</h2>
<p>A change was introduced during the 0.9.5 cycle to allow I2P's configuration files to be edited with the standard
Windows text editor, <code>Notepad</code>. This change had the unfortunate side-effect of causing our I2P site migration code to
fail to run on Windows systems, leading to I2P sites being served from the installation directory. Consequently:
Windows text editor, <code>Notepad</code>. This change had the unfortunate side-effect of causing our I2P Site migration code to
fail to run on Windows systems, leading to I2P Sites being served from the installation directory. Consequently:
</p>
<ul>
<li>depending upon how I2P is started, the I2P site may not be accessible; and</li>
<li>confusion ensues&mdash;all documentation states that I2P sites are served from the profile path; and</li>
<li>depending upon how I2P is started, the I2P Site may not be accessible; and</li>
<li>confusion ensues&mdash;all documentation states that I2P Sites are served from the profile path; and</li>
<li>the update to Jetty 7, included in the 0.9.6 release, will fail.</li>
</ul>
<p>While no action is required for users that are not hosting an I2P site (or are not using the included Jetty to host an I2P site), it is
recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P site in the future. If you are running an
I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
<p>While no action is required for users that are not hosting an I2P Site (or are not using the included Jetty to host an I2P Site), it is
recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P Site in the future. If you are running an
I2P Site it is important to follow this procedure prior to upgrading to 0.9.6.
</p>
<p>
@@ -46,20 +46,20 @@ I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
You should see something like the following:
<a href="{{ url_for('static', filename='images/ticket919/paths.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/paths.png') }}" /></a>
If the path at number 1 in the image above is set to <code>I2P site/jetty.xml</code>, the path needs to be updated.
If the path at number 1 in the image above is set to <code>I2P Site/jetty.xml</code>, the path needs to be updated.
</li>
<li>Click the <code>Edit</code> button next to <em>I2P webserver (I2P site)</em>. The page will reload to allow the path to be edited as shown below:
<li>Click the <code>Edit</code> button next to <em>I2P webserver (I2P Site)</em>. The page will reload to allow the path to be edited as shown below:
<a href="{{ url_for('static', filename='images/ticket919/edit.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/edit.png') }}" /></a>
Insert the full path to your I2P configuration directory <em>before</em> the text "I2P site/jetty.xml" as shown above,
Insert the full path to your I2P configuration directory <em>before</em> the text "I2P Site/jetty.xml" as shown above,
then click Click the <code>Save Client Configuration</code> button.
</li>
<li> If you're hosting an I2P site, move its contents to its proper home at <code>%APPDATA%\I2P\I2P site\docroot</code>.
<li> If you're hosting an I2P Site, move its contents to its proper home at <code>%APPDATA%\I2P\I2P Site\docroot</code>.
</li>
<li>At this point you should restart your I2P router.</li>
</ol>
<p>After following the steps outlined above, your I2P site will be served from <code>%APPDATA%\I2P\I2P site\docroot</code>
<p>After following the steps outlined above, your I2P Site will be served from <code>%APPDATA%\I2P\I2P Site\docroot</code>
and should be accessible at <a href="http://127.0.0.1:7658">http://127.0.0.1:7658</a>.
</p>
{% endblock %}