Space for Fakhrul Islam
Space for Fakhrul Islam
Breadcrumbs

Macdonal - Self Hosted Solution

Context

An engineering firm (client: M. McDonald) asked Eagle 3D Streaming to deploy a self-hosted version of the Eagle system inside their own infrastructure — instead of using Eagle’s cloud.

They are considering three types of deployments:

  1. Windows Virtual Machines (VMs)

  2. Linux Virtual Machines (VMs)

  3. Linux Containers





Main Discussion Points

1️⃣ Deployment Approach

  • The client is exploring Windows VMs, Linux VMs, or Linux Containers for the streamer setup.

  • Eagle 3D Streaming team doesn’t have experience with Linux containers yet.

  • The client may bring in their own North American container expert team to help.

  • Eagle’s developers (Simon & Shanzid) will coordinate with that team.





2️⃣ Self-Hosted Documentation

  • There’s an describing how the self-hosted system works.
    E3DS Solution and Architectural Document

  • AI-generated parts of the doc contain some inaccuracies, so Mohammad must review and fix it for correctness.

    • Especially sections on:

      • Virtual networks (VPC, VNet)

      • Firewall setup

      • DDoS protection (unclear or incomplete)

  • Review and update the document with real, accurate details.






3️⃣ Upload System (App Uploading)

  • The client wants to upload apps to their own Azure Blob Storage, not Eagle’s servers.

  • Eagle team previously did this for AWS, so similar logic might be reused for Azure.

  • Need to verify whether this Azure upload feature is implemented or not.

  • Aninda is working on an upload API that allows uploads without using the control panel.

  • After testing, documentation must be written on:

    • How upload via API works

    • What information the client needs to provide

    • How the upload system works technically






4️⃣ Infrastructure Components

  • The document should include accurate info about backend, frontend, and network setup.

  • Also include details on SSO (Single Sign-On) integration:

    • Aninda is making an SSO demo.

    • The document should explain how SSO works technically.

    • Mention that more detailed docs and demo are available on request.






5️⃣ Infrastructure Diagrams

  • The current Lucidchart diagrams are outdated and inaccessible.

  • Diagrams must be recreated in http://draw.io and reviewed for accuracy.








6️⃣ Authentication Flow (Client-Side Integration)

The client’s platform is called Moata.

  • Users log in to Moata’s dashboard (not Eagle’s).

  • Based on permissions, they see tiles (cards) for different streaming projects.

  • When they click a project tile → a new browser tab opens → it streams the project.

  • URLs must work with Eagle SDK, not just an iframe.

  • If a user tries to open a stream link directly without login, they should be redirected to the login page.






7️⃣ Showing Apps in Client’s Dashboard

  • Their dashboard (Moata) should show available streaming apps dynamically.

  • Ideally, new uploads in Eagle’s system should automatically appear as new tiles in their dashboard.

  • For now, it may need to be done manually, but Mohammad will check with Omi if it can be automated.

  • Whatever the final approach is → must be documented.