Website: move info about cloud storage into the main documentation

Move the info about using cloud storage from the FAQ to the Shared
Storage chapter of the documentation. The FAQ entry of the topic is now
reduced to a short answer + a link to the moved documentation.
This commit is contained in:
Sybren A. Stüvel 2024-01-23 10:27:19 +01:00
parent 27eb7be547
commit fd29f58c2e
2 changed files with 29 additions and 16 deletions

View File

@ -116,23 +116,11 @@ If you wish to contribute to the project, you're invited to
### 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).
In short: No. Sharing files using Syncthing, OwnCloud, Dropbox, Google Drive,
Onedrive, etc. is not supported by Flamenco. For more information, see [Cloud
Storage Services][cloud-storage].
[cloud-storage]: {{< ref "/usage/shared-storage" >}}#cloud-storage-services
## Troubleshooting

View File

@ -67,3 +67,28 @@ file you're submitting.
This requires a bit more to explain. See [Shaman Storage System][shaman].
[shaman]: {{< relref "shaman" >}}
## Cloud Storage Services
Sharing files using Syncthing, OwnCloud, Dropbox, Google Drive, Onedrive, etc.
is **not supported by Flamenco**.
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. Flamenco creates
a video from the rendered images; this also assumes that those images are
accessible after they've been rendered and saved to the storage.
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).
[jobtypes]: {{< ref "/usage/job-types" >}}