No real sync exists like you mention exists.
The closest solution is what I and a few others do. Using a cloud replication service, such as Micorosft OneDrive, Google Drive, Dropbox....
You put the catalog, all pictures, and make sure to include preferences and plugins in the same base folder, in the replication service. Now, everything will be replicated between the computers. However, and this is a big one, you CANNOT open Lr on the second computer until replication has finished between both computers. Otherwise, your catalog can become corrupted and/or end up with duplicate conflicts.
!time:5:17 from honey hole dragging the leg over for control to attack inside heel hook. elbow frame the other leg to bend it so hard to pull out, lean back and drag top leg over, then control the knee so they can't turn back over.
as mining becomes harder the essence of a decentralized currency no longer exists as specialized, centralized data centers exist to mine certain coins. Mining is consolidating more towards these data centers, so while it is still decentralized due to number of data centers around the world, it is not as decentralized as it could be should a PoS algorithm be used to validate new transactions
A good rule of thumb is that you want to have enough RAM to equal or exceed the sum of two things: The amount of memory that your programs take (including the max heap setting you give to Solr), and the size of your Solr index(es) stored on that server.
While using Lucene and Solr we are used to a very high reliability. However, there may come a day when Solr will inform us that our index is corrupted, and we need to do something about it. Is the only way to repair the index to restore it from the backup or do full indexation? No – there is hope in the form of CheckIndex tool.