yacy_search_server/htroot/ConfigNetwork_p.html
2007-05-10 11:15:55 +00:00

167 lines
9.7 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>YaCy '#[clientname]#': Network Configuration</title>
#%env/templates/metas.template%#
<script type="text/javascript">
<!--
function CheckForRobinson() {
var dist = document.ConfigForm.indexDistribute.checked;
var recv = document.ConfigForm.indexReceive.checked;
if(!(dist || recv)) {
//robinson-mode
document.ConfigForm.network[1].checked = true;
}
else {
//p2p-mode
document.ConfigForm.network[0].checked = true;
}
}
function EnableRobinson() {
if(document.ConfigForm.network[1].checked) {
document.ConfigForm.indexDistribute.checked = false;
document.ConfigForm.indexReceive.checked = false;
}
}
//-->
</script>
</head>
<body id="ConfigNetwork">
#%env/templates/header.template%#
#%env/templates/submenuConfig.template%#
<h2>Network Configuration</h2>
#(commit)#
::<div class="commit">Accepted Changes.</div>
::<div class="error">Inapplicable Setting Combination:</div>
#(/commit)#
#(commitCrawlPlea)#::<div class="error">P2P operation can run without remote indexing, but runs better with remote indexing switched on. Please switch 'Accept Remote Crawl Requests' on.</div>#(/commitCrawlPlea)#
#(commitDHTIsRobinson)#::<div class="error">For P2P operation, at least DHT distribution or DHT receive (or both) must be set. You have thus defined a Robinson configuration.</div>#(/commitDHTIsRobinson)#
#(commitDHTNoGlobalSearch)#::<div class="error">Global Search in P2P configuration is only allowed, if both, index receive and distribution is switched on. You have a P2P configuration, but are not allowed to search other peers.</div>#(/commitDHTNoGlobalSearch)#
#(commitRobinson)#::<div class="commit">For Robinson Mode, index distribution and receive is switched off.</div>#(/commitRobinson)#
#(commitRobinsonWithRemoteIndexing)#::<div class="commit">This Robinson Mode switches remote indexing on, but limits targets to peers within the same cluster. Remote indexing requests from peers within the same cluster are accepted.</div>#(/commitRobinsonWithRemoteIndexing)#
#(commitRobinsonWithoutRemoteIndexing)#::<div class="commit">This Robinson Mode does not allow any remote indexing (neither requests remote indexing, nor accepts it).</div>#(/commitRobinsonWithoutRemoteIndexing)#
<p>
You can configure if you want to participate at the global YaCy network or if you want to have your
own separate search cluster with or without connection to the global network. You may also define
a completely independent search engine instance, without any data exchange between your peer and other
peers, which we call a 'Robinson' peer.
</p>
<form name="ConfigForm" method="post" action="ConfigNetwork_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
<fieldset>
<legend>
<input type="radio" name="network" id="p2p" value="p2p"#(p2p.checked)#:: checked="checked"#(/p2p.checked)# />
<label for="p2p">Peer-to-Peer Mode</label>
</legend>
<dl>
<dt>
<label for="indexDistribute">Index Distribution</label>
<input type="checkbox" id="indexDistribute" name="indexDistribute" onclick="CheckForRobinson()" #(indexDistributeChecked)#::checked="checked" #(/indexDistributeChecked)#/>
</dt>
<dd>
This enables automated, DHT-ruled Index Transmission to other peers.<br />
<input type="radio" value="on" id="indexDistributeWhileCrawlingOn"
name="indexDistributeWhileCrawling"
#(indexDistributeWhileCrawling.on)#::checked="checked" #(/indexDistributeWhileCrawling.on)#/>
<label for="indexDistributeWhileCrawlingOn">enabled</label> /
<input type="radio" value="off" id="indexDistributeWhileCrawlingOff"
name="indexDistributeWhileCrawling"
#(indexDistributeWhileCrawling.off)#::checked="checked" #(/indexDistributeWhileCrawling.off)#/>
<label for="indexDistributeWhileCrawlingOff">disabled during crawling</label>.
</dd>
<dt>
<label for="indexReceive">Index Receive</label>
<input type="checkbox" id="indexReceive" name="indexReceive" onclick="CheckForRobinson()" #(indexReceiveChecked)#::checked="checked" #(/indexReceiveChecked)#/>
</dt>
<dd>
Accept remote Index Transmissions.<br />
This works only if you have a senior peer. The DHT-rules do not work without this function.<br />
<input type="radio" value="on" id="indexReceiveBlockBlacklistOn"
name="indexReceiveBlockBlacklist"
#(indexReceiveBlockBlacklistChecked.on)#::checked="checked" #(/indexReceiveBlockBlacklistChecked.on)#/>
<label for="indexReceiveBlockBlacklistOn">reject</label> /
<input type="radio" value="off" id="indexReceiveBlockBlacklistOff"
name="indexReceiveBlockBlacklist"
#(indexReceiveBlockBlacklistChecked.off)#::checked="checked" #(/indexReceiveBlockBlacklistChecked.off)#/>
<label for="indexReceiveBlockBlacklistOff">accept transmitted URLs that match your blacklist</label>.
</dd>
<dt>
<label for="crawlResponse">Accept Remote Crawl Requests</label>
<input type="checkbox" id="crawlResponse" name="crawlResponse" #(crawlResponse)#::checked="checked" #(/crawlResponse)#/>
</dt>
<dd>
Perform web indexing upon request of another peer.<br />
This works only if you are a senior peer.<br />
<label for="acceptCrawlLimit">Load with a maximum of</label>
<input id="acceptCrawlLimit" name="acceptCrawlLimit" type="text" size="3" maxlength="3" value="#[acceptCrawlLimit]#" /> pages per minute
</dd>
</dl>
</fieldset>
<fieldset>
<legend>
<input type="radio" name="network" id="robinson" onclick="EnableRobinson()" value="robinson"#(robinson.checked)#:: checked="checked"#(/robinson.checked)# />
<label for="robinson">Robinson Mode</label>
</legend>
<p class="help">
If your peer runs in 'Robinson Mode' you run YaCy as a search engine for your own search portal without data exchange to other peers.
There is no index receive and no index distribution between your peer and any other peer.
In case of Robinson-clustering there can be acceptance of remote crawl requests from peers of that cluster.
</p>
<dl>
<dt>
<label for="privatepeer">Private Peer</label>
<input type="radio" id="privatepeer" value="privatepeer" name="cluster.mode"
#(privatepeerChecked)#::checked="checked" #(/privatepeerChecked)#/>
</dt>
<dd>Your search engine will not contact any other peer, and will reject every request.
</dd>
<!-- not yet implemented
<dt>
<label for="cluster.modePrivatecluster">Private Cluster</label>
<input type="radio" value="privatecluster" id="cluster.modePrivatecluster" name="cluster.mode"
#(privateclusterChecked)#::checked="checked" #(/privateclusterChecked)#/>
</dt>
<dd>
Your peer is part of a private cluster without public visibility.<br />
Index data is not distributed, but remote crawl requests are distributed and accepted from your cluster.<br />
Search requests are spread over all peers of the cluster, and answered from all peers of the cluster.<br />
List of ip:port - addresses of the cluster: (comma-separated)<br />
<input type="text" name="cluster.peers.ipport" value="#[cluster.peers.ipport]#" size="80" maxlength="800" />
</dd>
-->
<dt>
<label for="cluster.modePubliccluster">Public Cluster</label>
<input type="radio" value="publiccluster" id="cluster.modePubliccluster" name="cluster.mode"
#(publicclusterChecked)#::checked="checked" #(/publicclusterChecked)#/>
</dt>
<dd>
Your peer is part of a public cluster within the YaCy network.<br />
Index data is not distributed, but remote crawl requests are distributed and accepted<br />
Search requests are spread over all peers of the cluster, and answered from all peers of the cluster.<br />
List of .yacy or .yacyh - domains of the cluster: (comma-separated)<br />
<input type="text" name="cluster.peers.yacydomain" value="#[cluster.peers.yacydomain]#" size="80" maxlength="800" /><br />
#[cluster.peers.yacydomain.hashes]#
</dd>
<dt>
<label for="cluster.modePublicpeer">Public Peer</label>
<input type="radio" value="publicpeer" id="cluster.modePublicpeer" name="cluster.mode"
#(publicpeerChecked)#::checked="checked" #(/publicpeerChecked)#/>
</dt>
<dd>
You are visible to other peers and contact them to distribute your presence.<br />
Your peer does not accept any outside index data, but responds on all remote search requests.
</dd>
<dt><label for="peertags">Peer Tags</label></dt>
<dd>
When you allow access from the YaCy network, your data is recognized using keywords.<br />
Please describe your search portal with some keywords (comma-separated).<br />
<input type="text" id="peertags" name="peertags" value="#[peertags]#" size="40" maxlength="80" />
</dd>
</dl>
</fieldset>
<input type="submit" name="save" value="Save" />
</form>
#%env/templates/footer.template%#
</body>
</html>