authorization and file-based security #153
Unanswered
samuelstroschein
asked this question in
[lix SDK] Feature Requests
Replies: 1 comment
-
Implementing a custom git server with auth as code like https://www.osohq.com/ could enable the feature. The cumbersome authorization path, see (reversed) #303, could simultaneously be streamlined by leveraging such a git server as auth layer. Inlang itself would only operate on that custom git server which maintains a sync with the origin repository e.g. a push to an inlang git server forwards the push to the origin git server. The inlang git server and SDK could turn into a proper BaaS over time while maintaining git sync. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The editor clones a whole repository. Especially for private repositories, file-based access control is desired. A translator should only be able to clone translation relevant files.
Beta Was this translation helpful? Give feedback.
All reactions