cep-promise VS isomorphic-git

A microcosm of the wasm issue was captured in this thread about implementing a web based git in JavaScript from scratch vs. compiling libgit

https://github.com/isomorphic-git/isomorphic-git/issues/268

I think one big missing part still with static sites is how you host the CMS to edit it.

Correct me if I'm wrong but Decap CMS (previously Netlify CMS) runs in the browser and makes reads/edits via GitHub which can then trigger rebuilds and deploys, but it still needs a small server/proxy I think because CORS stops your browser communicating directly with the GitHub API. Netlify hosts a GitHub backend that proxies requests for you but now you're tied to Netlify.

GitLab and BitBucket will have the same issue I think: https://github.com/isomorphic-git/isomorphic-git#cors-suppor...

Is there a simple solution here with minimal configuration?

ssh isn't supported on mobile for technical reasons

This article is an attempt to classify knowledge about using git in a nodejs environment. Particularly, this is going to tell about isomorphic-git library and how to implement it in web applications.

I recently had to implement git cloning into a full stack project and I found a very useful library OP can use. isomorphic-git which would solve this issue and allow them to clone into a virtual filesystem which can help save speed, storage, and possibly keep it secure. Plus if the memfs package is used the OP can just dumb the JSON of the Volume object into the request.

I always wanted to make a command line interface/prompt but didn't actually start it till a few months ago. I decided to go with Xterm.js for the basic terminal interface along with a modified local-echo to add basic required functionality. Then I set about duplicating every command I could find. I was able to link the terminal directly to the file system so all commands show real information. You can run help to view all commands/aliases. I've also included things such as Git, Python & Wapm.io support.