Re:Atom-in-orbit: Putting Atom in the browser
by tfn on Friday December 30, 2016 @08:21AM
(#13284216)
I discussed this with Tim Caswell, author of js-git, here in this podcast episode: http://episodes.gitminutes.com/2015/04/gitminutes-34-tim-cas...
I promptly reached out to GitLab, but I guess at the time they hadn't found it to be a use-case worth the trouble: https://twitter.com/gitlab/status/572860578646999040?cn=cmVw...
Re:Atom-in-orbit: Putting Atom in the browser
by scottlu2 on Thursday December 29, 2016 @06:52PM
(#13281300)
Try GHEdit, which is web based VSCode over your github repos:
Re:Atom-in-orbit: Putting Atom in the browser
by oweiler on Thursday December 29, 2016 @03:54PM
(#13280050)
You can always use a reverse-proxy to circumvent CORS.
Re:Atom-in-orbit: Putting Atom in the browser
by Klathmon on Thursday December 29, 2016 @04:01PM
(#13280092)
But then you're back to needing to run your own proxy server as it's also going to have to terminate SSL and therefore will be able to read everything that goes through it.
For this to be truly useful, it needs to embrace the "go to a URL and it works" paradigm of the web. If I need to install something locally, or setup a proxy server, or install some code on my git server, it's a non-starter to me.
Proxying to a server is annoying and ugly (and requires an always on connection to do anything substantial), and loading from the local filesystem is slow, complicated, and difficult to use and re-save. But I think there could be a really powerful way of solving this problem that I haven't seen mentioned anywhere else.
Work directly from a hosted git repo over HTTPS.
It would require a re-implementation of a subset of git in javascript, but from there you could plug it into the BrowserFS as a backing store, and you could then work directly from a git repo (and not just from a "blessed" git backend, but from any git backend that provides "git-over-https"). Loading files from there, saving them locally in indexeddb or something, then committing them back to the repo when ready.
I've only given this a minute or so of thought, so please tell me if i'm missing something big here.
Edit:
Giving it a little bit more time, it looks like a js reimplementation of enough of git for my uses already exists [0], and there seem to be at least 3 others as well. But in the notes he mentions that CORS is not and most likely won't be enabled for github which could be a problem. However that's not really a technical problem but more of a "political" one. If something like this became popular and perhaps other hosted git solutions (like GitLab) decided to allow you to enable CORS per account or repo or something, it could light a fire under GitHub's ass to allow it.
[0] https://github.com/creationix/js-git