ggstream-app / frontend Goto Github PK

Need a logo and other branding

Might also be on Create

Redirects to /admin/streams?url=personal instead of /admin/personal/streams

Need to create an actual UI that is not basic, unstyled ASP.net pages

Remove required tag, and add some ifs around the subtitles

• Add AI JS telemetry
• Add sensible tracing through the code
• Try and figure out how to log current viewer counts

Use in admin page, next stream page, etc

Infrastructure as code offering one-click region creation:

• Create RG with

  • Name ggstream-edge-{region}

• Create Edge VM with:

  • Name ggtream-edge-{location}, Ubuntu 18.04 in RG ggstream-edge-{region}
  • IP address ggtream-edge-{location}-ip, statically assigned, with DNS label ggtream-edge-{location}
  • NSG ggstream-edge-{location}-nsg has three new rule
    • 3334 WebRTC (310)
    • 8443 HLS/DASH (320)
    • 10000-10005/udp WebRTC ICE (330)
  • System-managed identity with AcrPull role on ggstream-docker
  • Add TrafficManager entry
    • ggstream-svc -> ggstream-edge-{location}-ip
  • If possible, DNS entry in CloudFlare
    • A svc-az{location}.ggstream.app -> ggstream-edge-{location}-ip

Current and Future GGStream Nodes

Redirect to a custom page which gives the schedule for the future ("starts in 20 minutes") using something akin to Humanizr (but for .net core) and "Stream has ended" for past streams (maybe with next public stream)

This is the mega-issue that tracks the authentication and authorization story for GGStream.
Currently, authentication is based on a single AAD tenant and grants the user access to all streams and collections, private (unlisted) or not.

AuthN

• Open login to other AAD tenants and MSA
• Create User model linked to AAD/MSA identity
• Users automatically have an entry created on first login, cannot pre-create accounts

AuthZ

• User can receive global Creator and Administrator roles
  • Creators can create new collections, receive Administrator permissions to created collections
  • Global Administrators have access to all collections and streams, and can perform any actions on them
• User can receive Viewer, Creator and Administrator roles on collections
  • Viewers receive Viewer role on all streams
  • Creators can create new streams, and edit or delete existing streams
  • Administrators can delete the collection
• User can receive Viewer role on streams
  • Viewers (Stream or Collection) can view the private stream, private or unlisted stream will appear on homepage
• Collections can be designated Public or Unlisted
  • Only work is to switch from a boolean to an enum (for futureproofing)
  • Existing functionality:
    • Public collections show up on the homepage, and the latest stream can be viewed directly at /{url} (Existing)
    • Unlisted collections show up only for those with a role, and require direct link to the stream
• Streams can be designated, Public, Unlisted or Private
  • Public streams will appear on the homepage
  • Unlisted streams (currently Private) will appear on the homepage only for users with Viewer, can be viewed by anyone with direct link
  • Private streams will appear on the homepage only for users with Viewer, require sign in and role to be viewed