SYNFIG STUDIO LESSON FULL
The full project repository is synced using some service, available for core collaborators only. So, what I want is to draw the difference: “keeping revision history” and “keeping project copies in sync” are two different tasks. The day-to-day sync includes transfer of much more data than you would like to have published in the final project, there are many junk changes, which we don’t want to appear in the commit history, and some of the data of it not intended to be published for wide audience at all. Many cloud sync services allow to exclude certain directories from sync, but we usually go with different approach, which is service-independent.īut first, let me clarify one thing: we use Git repositories when we publishing our sources, but we don’t use git repositories for day-to-day sync. So we need to sync everything except this directory. The rendered data always reside in the “render” subdirectory inside of the project root.
Rendering data could be produced (and updated) anytime from the sources, so it’s quite logical that we need to sync sources only, which dramatically reduces the bandwidth usage. Today I would like to share the workflow we use for that.įirst of all, as you probably know, for our projects we use Remake build system, which allows to separate sources from the rendered data.
When several people work on the animation project in different places, the project sources are usually synced between them using the cloud services.
0 kommentar(er)
