-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for plugging in custom storage backends #250
Comments
Could you please explain what you are trying to achieve? It's difficult to design an API without understanding concrete needs. |
I apologize for not providing enough details about the request. Currently, JSON files on the disk are used as persistent storage for group information (eg. group name, allowed users, wildcard users, etc.). Instead of having this information in JSON files on the disk I would like to use SQL database as a persistent storage. Similar for data/config.json. For recordings something similar could be available, so that video is not written directly on the FS but rather that I get a callback to my function (for each encoded frame or something similar). I've checked the code quite a bit, but I did not find such thing/api to be currently available in Galene, is this correct? I managed to get a POC of this working, but not sure if it is general or it is only for my use case:
And then for example in
I hope this better explains what I am trying to achieve. If not, I look forward to providing more information. |
It doesn't explain why you are doing this. What concrete problem are you trying to solve? I'm guessing that you are deploying Galene in an interesting manner, and that you cannot reasonably provide a writable filesystem. I need to understand your deployment before I can start having an opinion on your solution. |
Galene currently reads JSON files from the disk to get group information and server configuration. Maybe define a nice API to implement so that a custom backed for storing and reading group information can be used.
The text was updated successfully, but these errors were encountered: