Back to all discussions

  •   over 1 year ago

Do the judges need to see the code or is a functional website URL enough for them to try out?

Hi, I shared a website for consuming content and a subdomain for publishing content however I did not share my GitHub repo. Someone on Discord stated that the judges may want to read my code and as I submitted a full production webapp there is a lot more going on than just my theta integration.

As my Github repo is private I can give judges access to the serverside theta edge cloud functions if requested but I am unsure how to arrange this, if required. I have mentioned on my submission they can email me to request this if required.

Also, It wasn't mentioned anywhere in the rules that you had to share your code. It states 'link to a functioning demo app/video or URL to public code repository' with or being interpreted as you can submit a functioning app or a public repo, not both.

Regards, Bilal
vrtuhub

  • 2 comments

  • Manager   •   over 1 year ago

    It's not required, but it can be helpful for us to see that. Especially if it's not obvious from the demo where Theta is integrated. You can share it privately with GitHub username weslevitt if you prefer.

  •   •   over 1 year ago

    Okay it is done, Given access the git repo for the main site and team dashboard.
    website - https://github.com/Vrtuhub/Vrtuhub
    dashboard subdomain - https://github.com/Vrtuhub/Vrtuhub-dashboard

    I have also given access to the Server side functions for Theta Edge cloud
    Server Side functions
    Edge cloud webhook - https://github.com/Vrtuhub/thetaedge_webhook
    VOD function - https://github.com/Vrtuhub/thetaedge_appwrite
    Live Stream Function - https://github.com/Vrtuhub/theta_appwrite_function_livestream

    Notes:
    For the Server Side functions, the Entry Point is always main.js so you can ignore all those copies.
    You may also see a Livepeer SDK Imported however it is not being used anywhere. I was previously integrating with the Livepeer studio SDK but after feeling 'pushed out' by them for numerous reasons.

    There are numerous other server side functions such as email verification, like/dislike counters and livechat, a draft crypto payment processor with radom and some others but they arent edgecloud based or related in anyway so I have not shared them.

    ***
    I have have leaked API keys on the Server side functions as I did not expect to make this public (server-side code) as I was lazy with using .env so please do not share these around, however I will change the API keys at the end of this Hackaton.

Comments are closed.