You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
almereyda
changed the title
Adopt RemoteStorage, Solid and/or Fission as alternative storage backends
Consider alternative storage backends
Aug 10, 2022
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.
The text was updated successfully, but these errors were encountered: