Open almereyda opened 2 years ago
Together with "URL storage", and "remote URL sources" as suggested in #609, we could also consider to employ the sharing features of each of these providers, and have interacted schemes distributed with simple sharing of a URL (to schemio.app or custom deployments), that reference another URL, which is then being loaded and displayed.
I like this idea! Thanks! I did want to have more storage providers but didn't have enough time to work on that.
These ones should make it easy for you, as long as we consider that authentication and persistence are coupled here.
Also, another common provider that people could probably easily make use of, is S3. 🤯
Didn't think of that before, but if users provide valid credentials and endpoints to its HTTP API to the client, they would not even have to share the secret with Schemio server.
Through https://github.com/ishubin/schemio/issues/611#issuecomment-1210512036 I also remembered, that GitHub and GitLab also offer file storage and retrieval (into repositories) via their APIs.
Coming from the https://0data.app/ / http://unhosted.org/ / https://nobackend.org/ perspective, we know of alternative storage engines to Google Drive, which offer an authentication API plus trivial remote file storage for Browser clients.
Any of:
for example is able to store JSON files remotely, such as what we find in the
offlineScheme
object. Even a CouchDB connector, as presented with stackedit.io, could be considered.Such a support could offer to run online Schemio instances completely independent from Google's infrastructure.