first off: I am impressed with that ChatGPT support tool you have. I have never encountered something so persistently wrong about everything.
Which brings me to my question:
is there a way to directly connect two peers so they share their index? ChatGPT gave me 5 different possible ways to do that, none of which actually existed.
There is some documentation, which is also partial. But chat sucks, that’s true, IMHO. I suppose that was rather an experiment.
The easiest way would be to share one solr index. Either one standalone running solr for both instances, or let one instance to use solr index of the other. See docs.
Fair comment about ChatGPT inventing YaCy settings that don’t exist. I have had that..
For two YaCy peers, there isn’t a simple setting where you enter the other peer’s IP address and tell the two installations to permanently combine their complete indexes.
Normal YaCy P2P operation works through the distributed network and DHT rather than as a fixed peer-to-peer index mirror.
If your goal is specifically:
Peer A ----\
>---- same searchable index
Peer B ----/
then one practical option is to have both YaCy installations use the same Solr index — either an external/standalone Solr instance or one YaCy using the Solr service associated with the other installation.
That’s quite different from the normal YaCy public-peer DHT architecture.
I’ve been running multiple YaCy peers myself, so if you explain what you’re trying to achieve — two machines on a LAN, a private search network, redundancy, or simply making everything crawled by either machine searchable by both — we can probably work out the cleanest setup without inventing five imaginary menu options.
I exported all my crawl data from my desktop computer, nothing-is-secret, and imported that pack into Arkansas-notebook, and then both computers had the same document count, until a small crawl on one machine started, and added a small number of documents.
WARNING: Your machine may lose all its current documents if you import a pack from another machine. In my case, I had a backup, which I moved to a third machine, which is also online, so I did not lose any crawl data overall.
So, if you export a pack on one machine, and import it into another machine, both machines should at that moment have the exact same index, but not sharing in the sense that they are using the same hard drive or storage medium. So, if @ky0nshi is satisfied with two machines having the same index, then one could export its pack to the other.
Something I would like to test: Could you load two packs on one machine, and if you can, will your peer merge both together on the same machine?