Among all the cloud storages we've tried to use with Rclone, Azure Blobs turned out to be the fastest so far.
The bitter part of the story is that I did not know about Rclone existence until a recent year or two. I still feel ashamed about that.
Among all the cloud storages we've tried to use with Rclone, Azure Blobs turned out to be the fastest so far.
The bitter part of the story is that I did not know about Rclone existence until a recent year or two. I still feel ashamed about that.
Maybe to avoid uuids and use standard fs paths?
Gitea also has a private docker container registry built in, which quickly grows large into several (hundred) gigabytes. It all works perfectly well with rclone.
This makes my host stateless. Just run gitea docker image with Google-Drive backed storage. It works great because both git repositories and docker images are backed by files that are essentially immutable.
An example that would not work well would be trying to run a container whose storage is a SQLite file that updates often. Trying to sync that SQLite file to google drive with rclone would be a bad idea.
Such approach also protects you from a vendor lock-in: you can use any cloud storage you like today.
Performance drawbacks are evident - if a file is not cached in the local cache then it takes some time to get it there. But it does not really matter for the most apps because that initial lag is relatively short.
Reliability has been perfect so far.