Challenge Overview
This is the second PoC of a series to create a Git LFS server using AWS Codecommit. The first challenge we wanted to know if an existing LFS server could be used with AWS Codecommit - https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30064811.
In this challenge we want to create our own Git LFS server using Amazon AWS infrastructure to hold 3D assets.
- Detailed deployment guide on how to setup the amazon environments and deploy the code
In this challenge we want to create our own Git LFS server using Amazon AWS infrastructure to hold 3D assets.
Requirements:
- Create a server using the API definition found in https://github.com/git-lfs/git-lfs/tree/master/docs/api#readme. The API should be implemented using Amazon AWS API gateway and Lambda Functions.
- The server must support Server Discovery, Authentication, Batch API, Basic Adpter and File Locking;
- All large files should be saved to Amazon AWS S3 and versioned using AWS Codecommit
- API authentication should be done using API gateway;
- The system should allow at least clone, pull, push and commit operations;
- Demonstrate the server is working with AWS Codecommit and Git LFS client - https://git-lfs.github.com
References
These are reference implementations of a LFS server in different languages:- Git LFS test server - https://github.com/git-lfs/lfs-test-server (used in previous POC)
- LFS server with S3 integration - https://github.com/meltingice/git-lfs-s3
Final Submission Guidelines
- Zip file with the source code uploaded to Amazon AWS- Detailed deployment guide on how to setup the amazon environments and deploy the code