Sync Server
This page covers Sync Server: backend responsibilities, admin benefits and workflow with AC Sync.
Sync Server
Sync Server runs in the background on the server. It manages the content of your series, makes it available for AC Sync to download and can operate several areas cleanly separately.
Each series has its own folder with all the files needed.
The server automatically detects changes and keeps the file list up to date.
A server can run multiple instances at the same time, for example for live, test or league environments.
Can be operated securely over HTTPS, for example with nginx and certificate.
Why Sync Server
For admins, the biggest advantage is simple: content is stored cleanly once on the server and all drivers pick it up from there. You no longer have to maintain multiple download links, old archives and inquiries in the chat.
As soon as you change files in a series, the Sync Server creates new file lists with size, change time and SHA 256 checksum. AC Sync reliably detects what is missing or different on each driver machine.
Building new links, repackaging files and communicating to everyone costs extra time every time.
Without a central source, different versions quickly end up with different drivers.
A server can serve different instances by hostname, such as league, test server, or event.
Write accesses are protected, upload sizes can be limited and individual series can require a password.
For Leagues and Events
Sync Server turns many manual individual steps into a repeatable process. Drivers get the same content base, admins can prepare changes centrally, and new participants get up to speed faster.
Open Sync Server WikiWorkflow
AC Sync is the client on the driver's computer. The sync server is the central content source of the community. Both together ensure that everyone uses the same cars, tracks, skins and apps, without each driver having to collect files themselves.
Cars, tracks, skins or apps are placed in the server series folder.
The backend provides series and file checksums for AC Sync.
AC Sync only downloads what is missing or different.
All start with the expected content version.
There is a separate folder on the sync server for each series. There are, for example, cars, tracks, skins or apps. If anything changes, the admin doesn't need to send each driver a new guide. It updates the content in one place.
The sync server looks at the files and remembers file size, change time and checksum. You can think of this as a packing list: AC Sync will later see exactly which files belong to the series and which version is expected.
The driver selects the community server and the desired series. AC Sync then checks its own Assetto Corsa folder. Files that already exist correctly will be skipped. Only missing or outdated files are downloaded.
Fewer demands in the chat, fewer incorrect versions and less stress just before training. New drivers get into the grid faster, and regular drivers don't have to track every update manually.
The admin prepares the content, Sync Server tells AC Sync what is current, and AC Sync brings the driver folder to exactly that state.
