Skip to content

Latest commit

 

History

History
31 lines (23 loc) · 1.19 KB

File metadata and controls

31 lines (23 loc) · 1.19 KB

Versioning Notes

Notes:

Nov20th

cc_gateway api_gateway

  • The API gateway currenty has only 1 route called /snapshot which links to the lambda function below
  • Takes url query params userId, projectId and saveType
  • Also recieves code as base64 encoded string in request body

save_project_to_s3 lambda function

  • The lambda function recieves the userId, projectId, saveType (patch or snapshot) and the code
  • The lambda function stores the code file into the S3 bucket under the user and project
  • The code file is sent to the lambda function as a base64 encoded string and decoded in the lambda function
  • Based on the save_type the file is saved under /snapshot or /patch

Progress

  • Created s3 bucket
  • Created lambda with S3 execution full access permissions
  • Created API gateway

Dec10th

Update

  • The uploading to S3 and downloading from S3 flow is working - upload yjs data to S3 and getting the same data back. No corruption
  • Started work on patches - very similar flow

Next steps

  • I tested patches working on local. Now I think i need a /history route for getting last x updates
  • I also need to update the /snapshot route to apply patches on the latest update.