Website: add entry to FAQ about SyncThing/Dropbox/etc.
In short: such setups are not supported.
This commit is contained in:
parent
15e3745820
commit
51e1657f93
@ -58,6 +58,25 @@ If you have this working, please [share your job compiler script with us][getinv
|
|||||||
[getinvolved]: {{< ref "development/get-involved" >}}
|
[getinvolved]: {{< ref "development/get-involved" >}}
|
||||||
|
|
||||||
|
|
||||||
|
# Can I use SyncThing, Dropbox, Google Drive, or other file syncing software?
|
||||||
|
|
||||||
|
Flamenco assumes that once a file has been written by one worker, it is
|
||||||
|
immediately available to any other worker, like what you'd get with a NAS.
|
||||||
|
Similarly, it assumes that when a job has been submitted, it can be worked on
|
||||||
|
immediately.
|
||||||
|
|
||||||
|
Such assumptions no longer hold true when using an asynchronous service like
|
||||||
|
SyncThing, Dropbox, etc.
|
||||||
|
|
||||||
|
Note that this is not just about the initally submitted files. Also the
|
||||||
|
rendering of a preview video from individual images assumes that those images
|
||||||
|
are immediately accessible after they've been rendered.
|
||||||
|
|
||||||
|
It might be possible to create a complex [custom job type][jobtypes] for this,
|
||||||
|
but that's all untested. The hardest part is to know when all necessary files
|
||||||
|
have arrived on a specific worker, without waiting for *all* syncing to be
|
||||||
|
completed (as someone may have just submitted another job).
|
||||||
|
|
||||||
## What do "Error: Cached job type is old" or "job type etag does not match" mean?
|
## What do "Error: Cached job type is old" or "job type etag does not match" mean?
|
||||||
|
|
||||||
This means that you have to click on the little "Refresh" icon next to the job type:
|
This means that you have to click on the little "Refresh" icon next to the job type:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user