Difference between revisions of "Gitbackend"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
Datastore should provide "CRUD" functionality. | Datastore should provide "CRUD" functionality. | ||
We can use [https://developer.github.com/v3/git/ github API] need discussions(Why/Why not) | We can use [https://developer.github.com/v3/git/ github API] need discussions(Why/Why not) | ||
| + | API have certain limitations like the git API limits the support of blobs up to 100 megabytes in size [https://developer.github.com/v3/git/blobs/ proof], number of requests per hour are limited(60 requests for unauthenticated requests[https://developer.github.com/v3/#rate-limiting proof]. So it is better to build the datastore from scratch. | ||
2. Desigin UI | 2. Desigin UI | ||
UI should allow user to perform following activies in database: | UI should allow user to perform following activies in database: | ||
* fork | * fork | ||
| + | * clone | ||
* pull request | * pull request | ||
* merge | * merge | ||
| − | * see | + | * versioning(see history) |
Revision as of 12:00, 14 March 2015
Git Backend
The project is aimed to develop a git based backend for Journal.
Steps to move on this project:
1. Code to use git as datastore
Datastore should provide "CRUD" functionality. We can use github API need discussions(Why/Why not) API have certain limitations like the git API limits the support of blobs up to 100 megabytes in size proof, number of requests per hour are limited(60 requests for unauthenticated requestsproof. So it is better to build the datastore from scratch.
2. Desigin UI
UI should allow user to perform following activies in database:
* fork
* clone
* pull request
* merge
* versioning(see history)