You are viewing a single comment's thread.

view the rest of the comments →

0
1

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

WOWOWOWOW this is complete and utter overkill, overengineering and/or overthinking.

You don't need 99% of what is in your comment if you host on literally any static content host (think CDN). Manage your content as literally any data structure that is human readable on disk. Maybe a directory per person and within that a text file providing the video's description and embed URLs. Write some simple javascript to navigate this. Store all this in a git repo. When code is pushed to the repo use a webhook to trigger the code's deployment on the CDN. Look, your followers can even submit videos using pull requests too.

Pay me a couple thousand and I'll build you this in a weekend.

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
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.