Difference between revisions of "Gitbackend"

Revision as of 06:00, 5 April 2015

The project is aimed to develop a git based backend for Journal.

Functional Requirements

Users(kids) should be able to:

The dia file of above workflow is present here.

1. Code to use git as datastore

   Datastore should provide "CRUD" functionality.

@@ Line 24: / Line 24: @@
 The dia file of above workflow is present [https://drive.google.com/file/d/0B-LVD_AaEDFjSkZoMVgwT3VFSnM/view?usp=sharing here].
-==== '''Steps to move on this project:''' ====
+=== '''Steps to move on this project:''' ===
 . Code to use git as datastore
      Datastore should provide "CRUD" functionality.
-    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.
-  Desigin UI
-    UI should allow user to perform following activies in database:
-        * fork
-        * clone
-        * pull request
-        * merge
-        * versioning(see history)