0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago 

I was thinking more about this last night and I think you are right.

I'm aiming to get a function demo site live by this evening, running just on CloudFlare and Github pages :)

0
1

[–] voice_of_reason 0 points 1 point (+1|-0) ago 

Cool. For creating an MVP I think this approach has plenty of flexibility. Let me know how it goes.

0
0

[–] jsprogrammer [S] ago 

I will. Github's bot has currently flagged my new organization as possible spam (or something; it's unclear). DNS and Cloudflare are all setup (though, no code is pushed), but I don't know when the GH issue will be resolved. A support ticket has been in for a little bit now.

The domain/site is: https://wiyr.us

The GH organization is: https://github.com/wiyr-us

I'll update you here when there is something to see.

0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago 

I could build this solution too. I think it could work for a very minimal version (I already run some projects in a similar manner), however, if you want to do anything with WebRTC, there are additional services that must be ran. Also, if you want multiple people to be able to edit the database (which I think is necessary), the approach won't scale that well.

0
0

[–] voice_of_reason ago  (edited ago)

Why would it not scale? Github was created by very intelligent people and I would think no matter how many people push or accept a pull request at once, their system will queue and handle it. Many very large software projects with hundreds of authors use github.

Since you are typically only adding NEW files, the git merges would be done automatically by github, on their end. No need for manually using git to approve each addition. The only time when human intervention is needed would be if two users edit the same file at once in a way that git cannot automatically resolve. But this would be a problem in an editing system of any scale.

0
0

[–] jsprogrammer [S] ago 

Oh, git itself can scale, but yeah, the scaling issue is with concurrent editing. I'll have to think if this can be done solely by adding files, but I think there at least needs to be an index that would need updating. Something like PostgreSQL can scale particular types of concurrent editing better than git. For now though, I'm going to see how far I can take the git only approach. I really like its replication "story".