Distributed Peer-to-Peer Web Search Engine and Intranet Search Appliance http://yacy.net/
Go to file
2023-02-24 17:50:29 +01:00
.github Update FUNDING.yml 2022-11-28 15:18:30 +01:00
addon attempt to make a Mac Release using gradle 2021-10-25 18:37:39 +02:00
bin fixed apicall call method parameters 2020-12-22 00:46:47 +01:00
defaults enabling new update location release.yacy.net 2022-12-05 14:26:17 +01:00
docker yacy is working in container 2023-01-29 14:51:45 +01:00
examples move example code SearchClient out of yacycore package 2016-03-14 02:22:06 +01:00
htroot added canonical filter 2023-01-16 14:50:30 +01:00
kubernetes removed Debian and Red Hat build process 2021-07-19 20:33:52 +02:00
langdetect Use language-detection library for increased accuracy 2015-07-02 18:41:13 +02:00
lib rm License files from lib/ folder 2022-04-08 18:33:20 +00:00
libbuild/J7Zip-modified Merge branch 'master' of https://github.com/yacy/yacy_search_server 2022-12-01 01:28:30 +01:00
libt use ivy to manage jars 2022-04-08 18:33:20 +00:00
LICENSES creating LICENSES directory 2021-03-11 12:16:37 +01:00
locales removed ContentControl servlet and functinality 2022-09-28 17:25:04 +02:00
skins added stub of rc3assembly style 2021-02-09 20:30:10 +01:00
snap Added a stop command using the existing stop script to the snap package 2019-02-04 14:34:37 +01:00
source increased network image size limit for linuxtage poster 2023-02-24 17:50:29 +01:00
test fix test xlsx file with correct anchor 2022-02-07 04:24:29 +01:00
vocabularies moved yacy.logging to defaults according to request in 2012-05-17 04:26:03 +02:00
.checkstyle problems with code style 2009-06-29 22:22:35 +00:00
.classpath moved more servlets to new location 2022-10-02 22:57:58 +02:00
.dockerignore added a dockerignore file 2020-12-29 20:19:45 +01:00
.env Removed unnecessary variables for local heroku run 2016-07-13 01:07:11 +02:00
.gitignore changed system to load build properties 2022-10-03 10:12:47 +02:00
.project removed ContentControl servlet and functinality 2022-09-28 17:25:04 +02:00
.travis.yml removed Xms java memory startup parameter 2021-07-19 20:04:11 +02:00
app.json Updated YaCy home page embedded links from http to https scheme 2018-05-22 17:46:12 +02:00
AUTHORS added flori and me 2008-06-13 10:05:31 +00:00
build.nsi fixed windows installer nsi file for latest release file names 2022-10-04 16:05:35 +02:00
build.properties new release number schema and CI processes: 2022-10-04 16:14:40 +02:00
build.xml removed warnings 2022-10-04 22:28:15 +02:00
CONTRIBUTING.md Add contributor guidelines; closes #214 2018-08-15 23:23:30 +07:00
COPYRIGHT updated copyright message; included LGPL for 'cora' and a warranty 2013-06-30 11:30:39 +02:00
fixMacBuild.sh attempt to make a Mac Release using gradle 2021-10-25 18:37:39 +02:00
getWin32MaxHeap.bat update for memory observer algorithm 2009-12-06 17:45:48 +00:00
gpl.txt initial load with yacy 0.36 2005-04-07 19:19:42 +00:00
Heroku.md fix typo 2022-11-06 00:14:13 +08:00
installYaCyWindowsService.bat removed Xms java memory startup parameter 2021-07-19 20:04:11 +02:00
ivy.xml possible fix for 2022-10-05 21:56:12 +02:00
killYACY.sh Fix for http://mantis.tokeek.de/view.php?id=432 2014-08-25 22:47:33 +02:00
lgpl21.txt migrated all my LGPL 3 -licensed files to the LGPL 2.1 because LGPL 3 is not compatible to the GPL 2 2010-06-28 16:25:14 +00:00
NOTICE * updated jxpath to latest v1.3 2009-07-15 16:13:24 +00:00
Procfile Simplified Heroku variables configuration 2016-07-28 02:04:51 +02:00
README.md link to english wiki 2023-02-11 12:38:23 +02:00
startYACY_debug.bat changed link to new forum location 2022-02-03 13:27:06 +01:00
startYACY.bat for some strange reason there is no javaw in temurin, only java 2022-10-06 00:11:04 +02:00
startYACY.sh changed link to new forum location 2022-02-03 13:27:06 +01:00
stopYACY.bat upd classpath in batches (remove not necessary htroot) 2016-02-03 21:50:50 +01:00
stopYACY.sh fixed apicall call method parameters 2020-12-22 00:46:47 +01:00
uninstallYaCyWindowsService.bat added Windows Service installer 2013-12-26 05:07:26 +01:00
updateYACY.sh fixed apicall call method parameters 2020-12-22 00:46:47 +01:00
yacy-packages.readme fix typo 2022-11-06 00:14:13 +08:00
yacy.yellow performance setting for remote indexing configuration and latest changes for 0.39 2005-07-22 13:56:19 +00:00

YaCy

Gitter Build Status Install Link

Deploy

What is this?

The YaCy search engine software provides results from a network of independent peers, instead of a central server. It is a distributed network where no single entity decides what to list or order it appears in.

User privacy is central to YaCy, and it runs on each user's computer, where search terms are hashed before they being sent to the network. Everyone can create their individual search indexes and rankings, and a truly customized search portal.

Each YaCy user is either part of a large search network (search indexes can be exchanged with other installation over a built-in peer-to-peer network protocol) or the user runs YaCy to produce a personal search portal that is either public or private.

YaCy search portals can also be placed in an intranet environment, making it a replacement for commercial enterprise search solutions. A network scanner makes it easy to discover all available HTTP, FTP and SMB servers.

To create a web index, YaCy has a web crawler for everybody, free of censorship and central data retention:

  • Search the web (automatically using all other YaCy peers)
  • Co-operative crawling; support for other crawlers
  • Intranet indexing and search
  • Set up your own search portal
  • All users have equal rights
  • Comprehensive concept to anonymize the users' index

To be able to perform a search using the YaCy network, every user has to set up their own node. More users means higher index capacity and better distributed indexing performance.

License

This project is available as open source under the terms of the GPL 2.0 or later. However, some elements are being licensed under GNU Lesser General Public License. For accurate information, please check individual files. As well as for accurate information regarding copyrights. The (GPLv2+) source code used to build YaCy is distributed with the package (in /source and /htroot).

Where is the documentation?

All these have (YaCy) search functionality combining all these locations into one search result.

Dependencies? What other software do I need?

You need Java 1.8 or later to run YaCy. (No Apache, Tomcat or MySQL or anything else)

YaCy also runs on IcedTea 3. See https://icedtea.classpath.org

Start and stop it

Startup and shutdown:

  • GNU/Linux and OpenBSD:

    • Start by running ./startYACY.sh
    • Stop by running ./stopYACY.sh
  • Windows:

    • Start by double-clicking startYACY.bat
    • Stop by double-clicking stopYACY.bat
  • macOS: Please use the Mac app and start or stop it like any other program (double-click to start)

The administration interface

A web server is brought up after starting YaCy. Open this URL in your web-browser:

http://localhost:8090

This presents you with the personal search and administration interface.

(Headless) YaCy server installation

YaCy will authorize users automatically if they access the server from its localhost. After about 10 minutes a random password is generated, and then it is no longer possible to log in from a remote location. If you install YaCy on a server that is not your workstation you must set an admin account immediately after the first start-up. Open:

http://<remote-server-address>:8090/ConfigAccounts_p.html

and set an admin account.

YaCy in a virtual machine or a container

Use virtualization software like VirtualBox or VMware.

The following container technologies can deploy locally, on remote machines you own, or in the 'cloud' using a provider by clicking "Deploy" at the top of the page:

Docker

More details in the docker/Readme.md.

Heroku

PaaS (Platform as a service) More details in Heroku.md.

Port 8090 is bad, people are not allowed to access that port

You can forward port 80 to 8090 with iptables:

iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8090

On some operating systems, access to the ports you are using must be granted first:

iptables -I INPUT -m tcp -p tcp --dport 8090 -j ACCEPT

Scaling, RAM and disk space

You can have many millions web pages in your own search index. By default, 600MB RAM is available to the Java process. The GC process will free the memory once in a while. If you have less than 100000 pages you could try 200MB till you hit 1 million. Here you can adjust it. Several million web pages may use several GB of disk space, but you can adjust it here to fit your needs.

Help develop YaCy

Join the large number of contributors that make YaCy what it is; community software.

To start developing YaCy in Eclipse:

  • clone https://github.com/yacy/yacy_search_server.git using build-in Eclipse features (File -> Import -> Git)
  • or download source from this site (download button "Code" -> download as Zip -> and unpack)
  • import a Gradle project (File -> Import -> Gradle -> Existing Gradle Project)
  • in the tab "Gradle Tasks" are tasks available to use build the project (e.g. build -> build or application -> run)

To start developing YaCy in Netbeans:

  • clone https://github.com/yacy/yacy_search_server.git (Team → Git → Clone)
    • if you checked "scan for project" you'll be asked to open the project
  • Open the project (File → Open Project)
  • you may directly use all the Netbeans build feature.

To join our development community, got to https://community.searchlab.eu

Send pull requests to https://github.com/yacy/yacy_search_server

Compile from source

The source code is bundled with every YaCy release. You can also get YaCy from https://github.com/yacy/yacy_search_server by cloning the repository.

git clone https://github.com/yacy/yacy_search_server

Compiling YaCy:

  • You need Java 1.8 and ant
  • See ant -p for the available ant targets

APIs and attaching software

YaCy has many built-in interfaces, and they are all based on HTTP/XML and HTTP/JSON. You can discover these interfaces if you notice the orange "API" icon in the upper right corner of some web pages in the YaCy web interface. Click it, and you will see the XML/JSON version of the respective webpage. You can also use the shell script provided in the /bin subdirectory. The shell scripts also call the YaCy web interface. By cloning some of those scripts you can easily create more shell API access methods.

Contact

Visit the international YaCy forum where you can start a discussion there in your own language.

Questions and requests for paid customization and integration into enterprise solutions. can be sent to the maintainer, Michael Christen per e-mail (at mc@yacy.net) with a meaningful subject including the word 'YaCy' to prevent it getting stuck in the spam filter.

  • Michael Peter Christen