Cool idea! Was going to ask about performance and handling async actions but then I read the last paragraph:)
I wonder if this would actually suit another use case other than small hacking projects...
Another thought: you’d probably want to think about encryption at rest.
And a last one: you never keep an open connection like with a standard data store which means that in the slightest scale / network load on your git provider data could get lost or conflicts may occure when you sync.
Thought provoking stuff! Cool work !
Thx.
Data is stored in text files, so it would be possible to use ordinary fs protection like BitLocker or EFS (at least on Windows) for encryption. Of course, you have to trust your GIT provider (Github/Bitbucket). Otherwise, it should be possible to use things like git-crypt, but I never tried it out.
Regarding losing data, I`m not entirely sure what you mean because I never encountered a problem, where I would lose data during git push. Well.. few times it happened, that auto-merge in Git made wrong decisions – usually in case of CSS files, but that is easily solvable thanks to full history.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cool idea! Was going to ask about performance and handling async actions but then I read the last paragraph:)
I wonder if this would actually suit another use case other than small hacking projects...
Another thought: you’d probably want to think about encryption at rest.
And a last one: you never keep an open connection like with a standard data store which means that in the slightest scale / network load on your git provider data could get lost or conflicts may occure when you sync.
Thought provoking stuff! Cool work !
Thx.
Data is stored in text files, so it would be possible to use ordinary fs protection like BitLocker or EFS (at least on Windows) for encryption. Of course, you have to trust your GIT provider (Github/Bitbucket). Otherwise, it should be possible to use things like git-crypt, but I never tried it out.
Regarding losing data, I`m not entirely sure what you mean because I never encountered a problem, where I would lose data during git push. Well.. few times it happened, that auto-merge in Git made wrong decisions – usually in case of CSS files, but that is easily solvable thanks to full history.