Hi, I've been searching for some documentation about the Remote Everything indexes function, however I found but bits and pieces, so I've decided to ask here, creating a resource for others to use at the same time as well.
As far as I understand right now, Remote Everything indexes should connect to another everything app instance process running on a remote system, scanning local or remote file system on that given remote system, and enabling the user to search through its database seamlessly.
For this, it's required for the remote system to be running everything client service (ETP? Not sure what even ETP stands for??). viewtopic.php?t=1982
That said, if I recall correctly, even running everything normally, causes a request to open some ports in the Windows firewall.
I still feel like I'm missing the complete picture, tho: What username and password do I put in when adding a Remote Everything index? Local Windows account under which the Everything process is running? Does the process have to be Everything client service? Can I configure settings normally in a GUI on a remote server first, such as which folders to index? Or is it really configurable only by hand editing the ini file? Does the local everything instance that had a Remote Everything indexes defined cache these remote indexes to allow searching trough them even if the remote indexes are currently unreachable?
To avoid XY problem: I have a NAS at a remote location. I can scan it from a local Everything instance as I do now, but the indexing process takes much longer than usual due to the increased latency that doesn't play well with SMB. What can I do to avoid this? Remote Everything indexes, as I understand them right now, seem like just the solution to this issue. Just run it "locally" whether that means in a VM on the NAS itself, on a PC on the local LAN or possibly even in something like a docker container, and then just download and use the index for searching from there! I'm just not sure if that's actually what the Remote Everything indexes are for, and how exactly to set it all up and get it running.
Network Indexes / Remote Everything indexes
Re: Network Indexes / Remote Everything indexes
Everything has 2 types of network indexes:
(assuming you are in location A; NAS is in location B)
1. ETP
ETP runs at location B. Using the ETP client in location A gives remote access to the list of files/folders in B.
These entries will not be added to the local indezes in A.
Files can be downloaded and started (given the correct paths).
2. Everything Server.
Everything Server runs at B. Everything clients at A can "subscribe to the Everything Server in B.
They will get real-time updates from the Everything Server, to be added at their local indexes.
(an extra option: Everything in location B can also run a http webserver. That way files are accessible from a webbrowser in A.)
Which one would suit your needs best?
(assuming you are in location A; NAS is in location B)
1. ETP
ETP runs at location B. Using the ETP client in location A gives remote access to the list of files/folders in B.
These entries will not be added to the local indezes in A.
Files can be downloaded and started (given the correct paths).
2. Everything Server.
Everything Server runs at B. Everything clients at A can "subscribe to the Everything Server in B.
They will get real-time updates from the Everything Server, to be added at their local indexes.
(an extra option: Everything in location B can also run a http webserver. That way files are accessible from a webbrowser in A.)
Which one would suit your needs best?
Re: Network Indexes / Remote Everything indexes
Hey, thank you for the reply!
I still seem to be failing at identifying the key differences between the ETP and Everything Server.
Maybe a more detailed example would help us decide which option would suit my situation better.
Right now I just have network folders such as \\DSM1\ defined in [Tools -> Options -> Indexes -> Network Drives]. Due to way the VPN I'm using works, I can always reach the same NAS on \\DSM1 regardless of whether I am on LAN or Away connected via the Internet. However, when I'm away, the scans of \\DSM1 take too long.
Anyway, right now, when I search for a file, some results can show me a file in \\DSM1\… and I can normally open these files from the results list. (Or in case I'm offline, the file entries are just grayed out) My goal is to end up with exactly the same experience, except the scanning / indexing should happen on a remote server that's always “directly connected” to my NAS.
Since it sounds to me like ETP downloads files on demand, being basically a proxy, the Everything Server appears like a better option for my use-case, but I feel like you'll know better than me.
Let me know if you'd like me to provide any more info~!
I still seem to be failing at identifying the key differences between the ETP and Everything Server.
Maybe a more detailed example would help us decide which option would suit my situation better.
Right now I just have network folders such as \\DSM1\ defined in [Tools -> Options -> Indexes -> Network Drives]. Due to way the VPN I'm using works, I can always reach the same NAS on \\DSM1 regardless of whether I am on LAN or Away connected via the Internet. However, when I'm away, the scans of \\DSM1 take too long.
Anyway, right now, when I search for a file, some results can show me a file in \\DSM1\… and I can normally open these files from the results list. (Or in case I'm offline, the file entries are just grayed out) My goal is to end up with exactly the same experience, except the scanning / indexing should happen on a remote server that's always “directly connected” to my NAS.
Since it sounds to me like ETP downloads files on demand, being basically a proxy, the Everything Server appears like a better option for my use-case, but I feel like you'll know better than me.
Let me know if you'd like me to provide any more info~!