Adding new backends #1753
-
|
I'm wondering how feasible it is to implement a new backend. It seems like there are already many implementations, so it should be fairly straightforward to add a new one, right? (Or is it?) In particular, I'm thinking at some point it would be great to add a cloud provider as a backend (such as Nextcloud, Dropbox, Google Drive, etc.). There is already a file backend, so I suppose it could work the same way, only slower. What considerations should one have before attempting something like this? (I don't think I'll work on that any time soon, but maybe I do in the future). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Implementing the DataAccessor interface is sufficient. This repo contains an implementation for a Redis backend for example: https://github.com/comake/solid-redis/. It was made for an older version of CSS so config-wise there have been some changes, but the idea is still the same. |
Beta Was this translation helpful? Give feedback.
-
|
That's nice, it seems very straightforward :). Thanks! |
Beta Was this translation helpful? Give feedback.
Implementing the DataAccessor interface is sufficient.
This repo contains an implementation for a Redis backend for example: https://github.com/comake/solid-redis/. It was made for an older version of CSS so config-wise there have been some changes, but the idea is still the same.