- removed settings that are in Basic Settings - joined pages that belong together - moved include pages from yacy/ to / git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@2726 6c8d7289-2bf4-0310-a012-ef5d649a1542pull/1/head
orbiter
18 years ago
parent
25ae3d3161
commit
2e4aa6a170
@ -1,20 +0,0 @@
|
||||
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
|
||||
<fieldset><legend id="admin">Administration Account Settings</legend>
|
||||
<p>This is the account that restricts access to this 'Settings' page. If you have not customized it yet, you should do so now:
|
||||
<p><table border="0" cellspacing="5">
|
||||
<tr valign="top">
|
||||
<td>Account Name:</td><td><input name="adminuser" type="text" size="16" maxlength="16" value="#[adminuser]#"></td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td>Password:</td>
|
||||
<td><input name="adminpw1" type="password" size="16" maxlength="16" value=""></td></tr>
|
||||
<tr valign="top">
|
||||
<td>Password (repeat same as above):</td>
|
||||
<td><input name="adminpw2" type="password" size="16" maxlength="16" value=""></td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2"><input type="submit" name="adminaccount" value="submit"></td>
|
||||
</tr>
|
||||
</table>
|
||||
</fieldset>
|
||||
</form><br>
|
||||
@ -1,28 +0,0 @@
|
||||
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
|
||||
<fieldset><legend id="general">General Settings</legend>
|
||||
<p>
|
||||
<table border="0" cellspacing="5">
|
||||
<tr valign="top">
|
||||
<td>Peer Name:</td>
|
||||
<td><input name="peername" type="text" size="32" maxlength="80" value="#[peerName]#"></td>
|
||||
<td><b>Your peer name defines also a new '.yacy' - domain, which can be accessed from every peer running this proxy.</b>
|
||||
Using your 'Home Page' and 'File Share' - zones you also have a platform to provide content to your new domain.<br>
|
||||
<i>(hint: Choose a name that appears on a web page that tells something about you, visit the page, get the 'senior' status, and you can be found...)</i></td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td>staticIP (optional):</td>
|
||||
<td><input name="staticIP" type="text" size="32" maxlength="80" value="#[staticIP]#"></td>
|
||||
<td><b>The staticIP can help that your peer can be reached by other peers in case that your
|
||||
peer is behind a firewall or proxy.</b> You can create a tunnel through the firewall/proxy
|
||||
(look out for 'tunneling through https proxy with connect command') and create
|
||||
an access point for incoming connections.
|
||||
This access address can be set here (either as IP number or domain name).
|
||||
If the address of outgoing connections is equal to the address of incoming connections,
|
||||
you don't need to set anything here, please leave it blank.<br>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="3"><input type="submit" name="generalsettings" value="submit"></td>
|
||||
</tr>
|
||||
</table>
|
||||
</fieldset>
|
||||
</form><br>
|
||||
@ -1,25 +1,51 @@
|
||||
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
|
||||
<fieldset><legend id="ServerAccess">Server Access Settings</legend>
|
||||
<p>Here you can restrict access to the server. By default, the access is not limited, because this function is needed to spawn the p2p index-sharing function. If you block access to your server (setting anything else than '*'), then you will also be blocked from using other peers' indexes for search service. However, blocking access may be correct in enterprise environments where you only want to index your company's own web pages.</p>
|
||||
<p>ATTENTION: Your current IP is recognized as "#[clientIP]#". If the value you enter here does not match with this IP, you will not be able to access the server pages anymore</p>
|
||||
<fieldset><legend id="general">General Settings</legend>
|
||||
<p>
|
||||
<table border="0" cellspacing="5">
|
||||
<tr valign="top">
|
||||
<td>IP-Number filter:</td>
|
||||
<td colspan ="2"><input name="serverfilter" type="text" size="50" maxlength="1000" value="#[serverfilter]#"></td>
|
||||
<tr valign="top">
|
||||
<td>IP-Number filter:</td>
|
||||
<td><input name="serverfilter" type="text" size="50" maxlength="1000" value="#[serverfilter]#"></td>
|
||||
<td><b>Here you can restrict access to the server.</b> By default, the access is not limited,
|
||||
because this function is needed to spawn the p2p index-sharing function.
|
||||
If you block access to your server (setting anything else than '*'), then you will also be blocked
|
||||
from using other peers' indexes for search service.
|
||||
However, blocking access may be correct in enterprise environments where you only want to index your
|
||||
company's own web pages.</td>
|
||||
</tr>
|
||||
<!--
|
||||
<tr valign="top">
|
||||
<td>Account Name:</td><td><input name="serveruser" type="text" size="16" maxlength="16" value="#[serveruser]#"></td>
|
||||
<td><input name="serveruser" type="text" size="16" maxlength="16" value="#[serveruser]#"></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td>Password:</td>
|
||||
<td><input name="serverpw1" type="password" size="16" maxlength="16" value=""></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td>Password (repeat same as above):</td>
|
||||
<td><input name="serverpw2" type="password" size="16" maxlength="16" value=""></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
-->
|
||||
<tr valign="top">
|
||||
<td valign="bottom" rowspan="3"><input type="submit" name="serveraccount" value="Submit"></td>
|
||||
<td>staticIP (optional):</td>
|
||||
<td><input name="staticIP" type="text" size="32" maxlength="80" value="#[staticIP]#"></td>
|
||||
<td><b>The staticIP can help that your peer can be reached by other peers in case that your
|
||||
peer is behind a firewall or proxy.</b> You can create a tunnel through the firewall/proxy
|
||||
(look out for 'tunneling through https proxy with connect command') and create
|
||||
an access point for incoming connections.
|
||||
This access address can be set here (either as IP number or domain name).
|
||||
If the address of outgoing connections is equal to the address of incoming connections,
|
||||
you don't need to set anything here, please leave it blank.<br>
|
||||
ATTENTION: Your current IP is recognized as "#[clientIP]#".
|
||||
If the value you enter here does not match with this IP,
|
||||
you will not be able to access the server pages anymore</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="3"><input type="submit" name="serveraccount" value="submit"></td>
|
||||
</tr>
|
||||
<!--
|
||||
<tr valign="top"><td>Password:</td><td><input name="serverpw1" type="password" size="16" maxlength="16" value=""></td></tr>
|
||||
<tr valign="top"><td>Password (repeat same as above):</td><td><input name="serverpw2" type="password" size="16" maxlength="16" value=""></td></tr>
|
||||
-->
|
||||
</table>
|
||||
</fieldset>
|
||||
</form><br>
|
||||
</form>
|
||||
Loading…
Reference in new issue