Hi, I’m facing an issue with AYON Site Sync in a multi-location setup. Our main studio uses a network drive for project storage, and the remote studio is also connected to it. Since working directly on that storage from the remote location is not feasible due to latency, I configured Site Sync with a local root override on the remote side (pointing to a local network storage at that location). Data published from the main studio pulls correctly to the remote site, but when I publish from the remote site, it does not sync back to the main studio. The database updates and files exist locally, but we cant pull them on the main storage. Am I missing something in the configuration, or is there an additional step required for uploads to trigger?
The settings are the same as yours. Additionally, I have configured a local root override with the remote site path, as without setting it, the system was considering the root path as the path for the secondary site.
I noticed that whenever I publish something from the secondary site, it gets published in the local override path, but in the AYON Browser and Site Sync web page it shows 0% / NA at the active site (which is the local site) and 100% at the remote site (which is the main site), which is incorrect. It should be the opposite, and this might be causing the issue.
Quick update:
After restarting the sync service earlier, the previously stuck files (N/A / Queued) got synced, and the --debug logs showed files copying from the remote site to the studio site.
However, after that, newly published files are again not syncing. So it looks like the restart processed the old backlog once, but the sync service is not continuously picking up new publishes.
Attaching our current artist remote settings and logs for reference. Could we be missing any setting required for continuous sync processing?
Yeah I believe this is the same issue i’ve ran in to. “Site Settings” are “Per User Site Settings”, you can change those settings there but thats only for YOUR active user and not for all users who logged into ayon, so you change those Site Settings overrides but another user will have different ones. This is all quite confusing, really. Sites and Site IDs are both used interchangable ( Sites can be Roots in the global Site Setting settings, but it can also be a “location” ), and its also not clear that these Site Settings overrides are available to be seen by all users and saved per user. The only global site configuration an admin is able to do is the projects Active/Remote defaults, and those are not “site aware”. I’m forking SiteSync myself now so we can get a clear per Site override going. Because currently SiteSync is only working reasonably for freelancers/home users and not for studio’s that provision machines with predetermined sites ( like hybrid cloud workflows. )
Hello,
Are you looking for a main root setting for all sites. and that one can be overridden in the site settings?
I mean
Project Anatomy Roots > override roots in project settings > override roots from project settings per site id
instead of
Project Anatomy Roots > override roots per site id