From 3f3c8055cb059700c60c8052784dbbc2acb625e6 Mon Sep 17 00:00:00 2001 From: adamsoffer Date: Tue, 4 Jun 2024 10:32:26 -0400 Subject: [PATCH 1/2] Rename sidebar titles for better readability --- developers/guides/livestream-from-browser.mdx | 4 +- developers/introduction.mdx | 2 +- developers/quick-start.mdx | 4 +- mint.json | 64 ++++++------------- sdks/introduction.mdx | 2 +- sdks/react/getting-started.mdx | 8 +-- sdks/react/migration/3.x/getting-started.mdx | 2 +- .../deploying.mdx | 2 +- .../developing-with-catalyst.mdx | 0 .../overview.mdx | 22 ++++--- .../self-hosting-with-docker.mdx | 2 +- 11 files changed, 45 insertions(+), 67 deletions(-) rename catalyst/deploying-catalyst.mdx => self-hosting/deploying.mdx (99%) rename {catalyst => self-hosting}/developing-with-catalyst.mdx (100%) rename catalyst/introduction.mdx => self-hosting/overview.mdx (59%) rename catalyst/running-catalyst.mdx => self-hosting/self-hosting-with-docker.mdx (98%) diff --git a/developers/guides/livestream-from-browser.mdx b/developers/guides/livestream-from-browser.mdx index 4a85fa4b..bac862a2 100644 --- a/developers/guides/livestream-from-browser.mdx +++ b/developers/guides/livestream-from-browser.mdx @@ -105,8 +105,8 @@ STUN/TURN servers to avoid network firewall issues. ## Adding custom broadcasting If you want to add custom broadcasting to your app and handle the WebRTC SDP -negotiation without using the React UI Kit primitives, you can follow the steps -below. +negotiation without using the Livepeer React primitives, you can follow the +steps below. ### Get the SDP Host diff --git a/developers/introduction.mdx b/developers/introduction.mdx index 7896cf4b..85a24eec 100644 --- a/developers/introduction.mdx +++ b/developers/introduction.mdx @@ -41,7 +41,7 @@ interacting with the Livepeer API. -### React UI Kit +### React Components -## React UI Kit +## React Components Build with composable React primitives for both broadcasting and playback. diff --git a/sdks/react/getting-started.mdx b/sdks/react/getting-started.mdx index 3efcf16c..a3ede5aa 100644 --- a/sdks/react/getting-started.mdx +++ b/sdks/react/getting-started.mdx @@ -1,14 +1,14 @@ --- title: "Getting Started" -description: "Get started building with the Livepeer React UI Kit." +description: "Get started building with Livepeer React" --- -Livepeer React UI Kit is a set of prebuilt and customizable UI primitives for -building live or on-demand video experiences. +Livepeer React is a set of prebuilt and customizable UI primitives for building +live or on-demand video experiences. ## Installation -Install Livepeer React UI Kit using your favorite package manager. +Install Livepeer React using your favorite package manager. ``` npm i @livepeer/react diff --git a/sdks/react/migration/3.x/getting-started.mdx b/sdks/react/migration/3.x/getting-started.mdx index d0b3940e..4bfa09b3 100644 --- a/sdks/react/migration/3.x/getting-started.mdx +++ b/sdks/react/migration/3.x/getting-started.mdx @@ -10,7 +10,7 @@ description: "Get started building with Livepeer UI Kit!" ## Installation -Install Livepeer React UI Kit using your favorite package manager. +Install Livepeer React using your favorite package manager. diff --git a/catalyst/deploying-catalyst.mdx b/self-hosting/deploying.mdx similarity index 99% rename from catalyst/deploying-catalyst.mdx rename to self-hosting/deploying.mdx index a17bc72d..73352791 100644 --- a/catalyst/deploying-catalyst.mdx +++ b/self-hosting/deploying.mdx @@ -1,5 +1,5 @@ --- -title: Deploying Catalyst +title: Deploying icon: cloud-arrow-up --- diff --git a/catalyst/developing-with-catalyst.mdx b/self-hosting/developing-with-catalyst.mdx similarity index 100% rename from catalyst/developing-with-catalyst.mdx rename to self-hosting/developing-with-catalyst.mdx diff --git a/catalyst/introduction.mdx b/self-hosting/overview.mdx similarity index 59% rename from catalyst/introduction.mdx rename to self-hosting/overview.mdx index df78dd36..a2fa92b4 100644 --- a/catalyst/introduction.mdx +++ b/self-hosting/overview.mdx @@ -1,26 +1,30 @@ --- -title: What is Catalyst? +title: Overview icon: flask --- -Catalyst is Livepeer's open-source, decentralized media server. It's built from -the same software stack that backs the Livepeer Studio hosted platform. +Livepeer Studio is powered by Catalyst, the Livepeer network's first +open-source, decentralized media server. Learn how to self-host Catalyst using a +single Docker command and get the full-stack Livepeer Studio experience running +on your laptop. -**Self-hosted Catalyst is in Alpha**, but we're excited for the first group of -hackers to start working on it! + + **Self-hosted Catalyst is in Alpha**, but we're excited for the first group of + hackers to start working on it! + ### Current capabilities: -- Boots up a full-stack Livepeer experience with a single command, either +- Boots up a full-stack Livepeer Studio experience with a single command, either locally or on a hosted server. -- Capable of transcoding on Livepeer mainnet. +- Capable of transcoding on the Livepeer mainnet. - Facilitates easy development of various components of the Livepeer stack. - Allows for development of applications against the Livepeer Studio API locally that can then transfer to the hosted version at [livepeer.studio](https://livepeer.studio) when you're ready to go to production. -- Bundles a fully-local offchain go-livepeer gateway and orchestrator, so - that you may test transcoding with no external dependencies. +- Bundles a fully-local offchain go-livepeer gateway and orchestrator, so that + you may test transcoding with no external dependencies. ### Current limitations: diff --git a/catalyst/running-catalyst.mdx b/self-hosting/self-hosting-with-docker.mdx similarity index 98% rename from catalyst/running-catalyst.mdx rename to self-hosting/self-hosting-with-docker.mdx index 674a76f2..0d6e0f1a 100644 --- a/catalyst/running-catalyst.mdx +++ b/self-hosting/self-hosting-with-docker.mdx @@ -1,5 +1,5 @@ --- -title: Running Catalyst Locally +title: Self-Hosting with Docker icon: person-running --- From 9856461a8c1623b494576d8ce1123d31aedf18a1 Mon Sep 17 00:00:00 2001 From: adamsoffer Date: Tue, 4 Jun 2024 11:24:57 -0400 Subject: [PATCH 2/2] more updates --- ai/contributors/guides/add-model.mdx | 2 +- ai/contributors/guides/add-pipeline.mdx | 2 +- developers/guides/livestream-from-browser.mdx | 7 ++- developers/guides/playback-a-livestream.mdx | 12 ++--- developers/guides/playback-an-asset.mdx | 12 ++--- developers/introduction.mdx | 21 ++++---- gateways/guides/gateway-overview.mdx | 2 +- mint.json | 51 +------------------ sdks/introduction.mdx | 12 ++--- sdks/react/broadcast/Camera.mdx | 4 +- sdks/react/broadcast/Enabled.mdx | 4 +- sdks/react/broadcast/Root.mdx | 7 ++- sdks/react/broadcast/Source.mdx | 4 +- sdks/react/migration/3.x/Player.mdx | 10 ++-- self-hosting/deploying.mdx | 7 ++- ...ith-catalyst.mdx => how-to-contribute.mdx} | 29 ++++++----- self-hosting/overview.mdx | 25 ++++----- 17 files changed, 75 insertions(+), 136 deletions(-) rename self-hosting/{developing-with-catalyst.mdx => how-to-contribute.mdx} (84%) diff --git a/ai/contributors/guides/add-model.mdx b/ai/contributors/guides/add-model.mdx index bb34a63e..6e39a32b 100644 --- a/ai/contributors/guides/add-model.mdx +++ b/ai/contributors/guides/add-model.mdx @@ -18,7 +18,7 @@ through the steps to add a new model to the AI Subnet. title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" - allowfullscreen + allowFullScreen > ## Step-by-Step Guide diff --git a/ai/contributors/guides/add-pipeline.mdx b/ai/contributors/guides/add-pipeline.mdx index e4bc2975..61b70fbb 100644 --- a/ai/contributors/guides/add-pipeline.mdx +++ b/ai/contributors/guides/add-pipeline.mdx @@ -19,7 +19,7 @@ through the steps to add a new pipeline to the AI Subnet. title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" - allowfullscreen + allowFullScreen > ## Step-by-Step Guide diff --git a/developers/guides/livestream-from-browser.mdx b/developers/guides/livestream-from-browser.mdx index bac862a2..225e6036 100644 --- a/developers/guides/livestream-from-browser.mdx +++ b/developers/guides/livestream-from-browser.mdx @@ -11,15 +11,14 @@ Livepeer Broadcast React component, or build their own WebRTC solution. ## Using UI Kit Broadcast The example below show to use the Livepeer UI Kit -[`Broadcast`](/sdks/react/broadcast/Root) component to broadcast from -the web. +[`Broadcast`](/sdks/react/broadcast/Root) component to broadcast from the web. ### Broadcast This guide assumes you have configured a Livepeer JS SDK client with an API key. -We can use the [`Broadcast`](/sdks/react/broadcast/Root) primitives -with a stream key, from a stream we created. +We can use the [`Broadcast`](/sdks/react/broadcast/Root) primitives with a +stream key, from a stream we created. We show some simple styling below with Tailwind CSS, but this can use any styling library, since the primitives ship as unstyled, composable components. diff --git a/developers/guides/playback-a-livestream.mdx b/developers/guides/playback-a-livestream.mdx index 26c0e5aa..bbaf980f 100644 --- a/developers/guides/playback-a-livestream.mdx +++ b/developers/guides/playback-a-livestream.mdx @@ -22,9 +22,9 @@ play a livestream. frameborder="0" width="100%" height="410" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen + webkitallowFullScreen + mozallowFullScreen + allowFullScreen /> ### Play Video @@ -275,7 +275,7 @@ Looping can also be set with `&loop=true`. frameborder="0" width="100%" height="410" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen + webkitallowFullScreen + mozallowFullScreen + allowFullScreen /> diff --git a/developers/guides/playback-an-asset.mdx b/developers/guides/playback-an-asset.mdx index 1b33722c..6c2c1766 100644 --- a/developers/guides/playback-an-asset.mdx +++ b/developers/guides/playback-an-asset.mdx @@ -23,9 +23,9 @@ styles to demonstrate what's possible. frameborder="0" width="100%" height="410" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen + webkitallowFullScreen + mozallowFullScreen + allowFullScreen /> ### Play Video @@ -268,7 +268,7 @@ set with `&loop=true`. frameborder="0" width="100%" height="410" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen + webkitallowFullScreen + mozallowFullScreen + allowFullScreen /> diff --git a/developers/introduction.mdx b/developers/introduction.mdx index 85a24eec..3dbf9b9b 100644 --- a/developers/introduction.mdx +++ b/developers/introduction.mdx @@ -1,22 +1,19 @@ --- title: Introduction -description: "Explore APIs, guides, and examples to integrate with Livepeer." +description: "Explore APIs, guides, and examples" icon: "hand-wave" --- -Livepeer is a video infrastructure network for live and on-demand streaming. -Designed to give developers the freedom to innovate, creators autonomy from -platforms, and viewers an incredible, low latency experience. +Livepeer Studio is your home for building, broadcasting, and publishing video +using the Livepeer Network. Effortlessly manage livestreams, video uploads, API +keys, network usage, billing, and more. - Get started with Livepeer in less than 5 minutes. - - - Learn about the core concepts of Livepeer. + Get started with Livepeer Studio in less than 5 minutes. - Learn how to integrate Livepeer into your app. + Learn how to add live or on-demand streaming into your app. -## Explore the Livepeer Dev Kit +## Explore the Livepeer Studio SDKs -The Livepeer Dev Kit is a set of SDKs, pre-built UI components, and tools for -interacting with the Livepeer API. +Explore developer SDKs, pre-built UI components, and tools for interacting with +the Livepeer Studio API. ### Server-side SDKs diff --git a/gateways/guides/gateway-overview.mdx b/gateways/guides/gateway-overview.mdx index c2e0a439..48668163 100644 --- a/gateways/guides/gateway-overview.mdx +++ b/gateways/guides/gateway-overview.mdx @@ -74,7 +74,7 @@ Working knowledge of system adminsitration tasks for your target platform are required. This guide provides directions for Linux, Windows, and Docker platforms. Familiarity with Livepeer protocol is beneficial. For more information view the go Livepeer -[installation guide.](//orchestrators/guides/install-go-livepeer) +[installation guide.](/orchestrators/guides/install-go-livepeer) This guide was developed using: diff --git a/mint.json b/mint.json index 4d1107c1..b8f3f99e 100644 --- a/mint.json +++ b/mint.json @@ -352,15 +352,10 @@ "url": "api-reference" }, { - "name": "Livepeer Dev Kit", + "name": "SDKs", "icon": "brackets-curly", "url": "sdks" }, - { - "name": "Self-Hosting", - "icon": "flask", - "url": "self-hosting" - }, { "name": "AI Video (Alpha)", "icon": "microchip-ai", @@ -513,15 +508,6 @@ ], "version": "Gateways" }, - { - "group": "Self-Hosting", - "pages": [ - "self-hosting/overview", - "self-hosting/self-hosting-with-docker", - "self-hosting/deploying", - "self-hosting/developing-with-catalyst" - ] - }, { "group": "AI Video", "pages": [ @@ -611,41 +597,6 @@ } ] }, - { - "group": "Core Concepts", - "icon": "notes", - "pages": [ - { - "group": "Livepeer Primitives", - "pages": [ - "developers/core-concepts/core-api/asset", - "developers/core-concepts/core-api/stream", - "developers/core-concepts/core-api/multistream", - "developers/core-concepts/core-api/access-control" - ] - }, - { - "group": "Livepeer Studio Dashboard", - "pages": [ - "developers/core-concepts/studio/webhooks", - "developers/core-concepts/studio/stream-health", - "developers/core-concepts/studio/in-browser-broadcast" - ] - }, - { - "group": "Livepeer Player", - "pages": ["developers/core-concepts/player/overview"] - }, - { - "group": "Livepeer Network", - "pages": [ - "developers/core-concepts/livepeer-network/delegators", - "developers/core-concepts/livepeer-network/orchestrators", - "developers/core-concepts/livepeer-network/gateways" - ] - } - ] - }, { "group": "Overview", "pages": ["sdks/introduction"] diff --git a/sdks/introduction.mdx b/sdks/introduction.mdx index 9a19e306..dc8e83e1 100644 --- a/sdks/introduction.mdx +++ b/sdks/introduction.mdx @@ -1,17 +1,11 @@ --- -title: "Livepeer Dev Kit" +title: "SDKs" description: - "The Livepeer Dev Kit is a set of SDKs, pre-built UI components, and tools for - interacting with the Livepeer API." + "Explore developer SDKs, pre-built UI components, and tools for interacting with +the Livepeer Studio API." sidebarTitle: "Introduction" --- - - We're aware that some API requests through the SDKs are not working as - expected. We're working on a fix and will update the documentation once it's - resolved. In the meantime, please use the REST API directly. - - ## Server-side SDKs Server-side SDKs reduce the amount of work required to use the Livepeer REST diff --git a/sdks/react/broadcast/Camera.mdx b/sdks/react/broadcast/Camera.mdx index 86d9336e..f50b7718 100644 --- a/sdks/react/broadcast/Camera.mdx +++ b/sdks/react/broadcast/Camera.mdx @@ -2,8 +2,8 @@ title: "Camera" description: "The `VideoEnabledTrigger` and `VideoEnabledIndicator` components provide - gateways with interactive controls and visual cues to manage the video - enabled state during a broadcast." + gateways with interactive controls and visual cues to manage the video enabled + state during a broadcast." icon: camcorder --- diff --git a/sdks/react/broadcast/Enabled.mdx b/sdks/react/broadcast/Enabled.mdx index e3018c89..ef3022ae 100644 --- a/sdks/react/broadcast/Enabled.mdx +++ b/sdks/react/broadcast/Enabled.mdx @@ -1,8 +1,8 @@ --- title: "Enable" description: - 'The `EnabledTrigger` and `EnabledIndicator` components provide gateways - with interactive controls and visual cues to manage the "enabled" state of the + 'The `EnabledTrigger` and `EnabledIndicator` components provide gateways with + interactive controls and visual cues to manage the "enabled" state of the broadcast.' icon: clapperboard --- diff --git a/sdks/react/broadcast/Root.mdx b/sdks/react/broadcast/Root.mdx index eb2cb897..f2e56ea0 100644 --- a/sdks/react/broadcast/Root.mdx +++ b/sdks/react/broadcast/Root.mdx @@ -78,10 +78,9 @@ typical media file playable by an HTML5 video element (MP4, WebM). Configures the WHIP WebRTC ingest URL for the `Broadcast` component. You can create the `ingestUrl` by passing -[`getIngest`](/sdks/react/broadcast/get-ingest) a string (interpreted -as a Livepeer Studio stream key or URL), Livepeer Studio stream data, or -Cloudflare stream data. `Broadcast` is compatible with all WHIP playback -endpoints. +[`getIngest`](/sdks/react/broadcast/get-ingest) a string (interpreted as a +Livepeer Studio stream key or URL), Livepeer Studio stream data, or Cloudflare +stream data. `Broadcast` is compatible with all WHIP playback endpoints. ```tsx {...} diff --git a/sdks/react/broadcast/Source.mdx b/sdks/react/broadcast/Source.mdx index f23192d1..432fd70e 100644 --- a/sdks/react/broadcast/Source.mdx +++ b/sdks/react/broadcast/Source.mdx @@ -1,8 +1,8 @@ --- title: "Source" description: - "The `SourceSelect` component provides gateways with a dropdown interface - to choose between different media source devices like cameras and microphones." + "The `SourceSelect` component provides gateways with a dropdown interface to + choose between different media source devices like cameras and microphones." icon: sliders --- diff --git a/sdks/react/migration/3.x/Player.mdx b/sdks/react/migration/3.x/Player.mdx index 8f3d1b2b..9a3c6bf6 100644 --- a/sdks/react/migration/3.x/Player.mdx +++ b/sdks/react/migration/3.x/Player.mdx @@ -92,9 +92,9 @@ or `useCreateStream`, and the `playbackId` was passed to the viewer. frameborder="0" width="100%" height="410" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen + webkitallowFullScreen + mozallowFullScreen + allowFullScreen > ## Compatibility @@ -1044,8 +1044,8 @@ to trigger preloading on upcoming videos, and automatically playing/pausing media when it is shown/hidden from the list. See our -[Expo sample app](https://github.com/livepeer/react/tree/main/examples/expo) -for a real-world example. +[Expo sample app](https://github.com/livepeer/react/tree/main/examples/expo) for +a real-world example. #### Usage diff --git a/self-hosting/deploying.mdx b/self-hosting/deploying.mdx index 73352791..ee068c5a 100644 --- a/self-hosting/deploying.mdx +++ b/self-hosting/deploying.mdx @@ -5,8 +5,7 @@ icon: cloud-arrow-up # Prerequisites -You'll need a few things to get started with deploying a publicly-accessible -Catalyst node: +You'll need a few things to get started: 1. A Linux server with a publicly-accessible IP address. 1. Docker, or another container runtime such as Podman. @@ -16,9 +15,9 @@ Catalyst node: 1. A reverse proxy with a valid TLS certificate. It should be configured to forward incoming traffic to `http://127.0.0.1:8888`. -# Running the image +# Running the Docker image -There are two required parameters to boot the Catalyst node: +There are two required parameters to run the Docker image: 1. `CATALYST_PUBLIC_URL`: This is the publicly-accessible address of your Catalyst node, including the `https` prefix, with no trailing slash. Example diff --git a/self-hosting/developing-with-catalyst.mdx b/self-hosting/how-to-contribute.mdx similarity index 84% rename from self-hosting/developing-with-catalyst.mdx rename to self-hosting/how-to-contribute.mdx index f28d0c26..aa8a7e67 100644 --- a/self-hosting/developing-with-catalyst.mdx +++ b/self-hosting/how-to-contribute.mdx @@ -1,9 +1,14 @@ --- -title: Developing with Catalyst +title: How to Contribute icon: gear --- -Developing Catalyst is currently supported on macOS and Linux. +Livepeer Studio is an open source project that is both under very active +development and is also being used to ship code to everybody on livepeer.studio. +We’re still working out the kinks to make contributing to this project as easy +and transparent as possible, but we’re not quite there yet. Hopefully this +document makes the process for contributing clear and answers some questions +that you may have. ### Dependencies @@ -18,7 +23,7 @@ You'll need the following things installed locally: - llvm (`brew install llvm` for compiling MistServer and go-livepeer on MacOS only) -You'll first need to clone the Catalyst repo if you haven't already. +You'll first need to clone the repo if you haven't already. ```shell git clone https://github.com/livepeer/catalyst.git @@ -41,8 +46,8 @@ make box-dev ``` Lots and lots of logs will print out while all the dependencies finish booting -up. After that, you'll now have a fully-functioning full-stack Livepeer Studio + -Catalyst environment running locally! You can access it like so: +up. After that, you'll now have a fully-functioning Livepeer Studio environment +running locally! You can access it like so: - URL: [http://localhost:8888](http://localhost:8888) - Email: `admin@example.com` @@ -50,8 +55,8 @@ Catalyst environment running locally! You can access it like so: ### Customizing the Environment -If you need to add additional parameters to things running inside the box, you -can create a `.env` file that contains key-value pairs: +If you need to add additional parameters to things running, you can create a +`.env` file that contains key-value pairs: ```shell echo "CATALYST_API_CDN_REDIRECT_PREFIX=https://externalcdn.livepeer.com/mist/" >> .env @@ -71,7 +76,7 @@ TLDR: Use a command like this and the Makefile will take care of it for you: make livepeer-catalyst-api ``` -The general Livepeer in a Box development cycle works like this: +The general development workflow works like this: 1. Make changes to code on your local filesystem 2. Build a Linux binary from that code @@ -119,10 +124,10 @@ commands: ### Connecting the Frontend -Livepeer in a Box comes with a [pkg](https://github.com/vercel/pkg)-bundled -version of the Livepeer Studio API server and frontend, but does not include a -full development environment for that frontend. If you are making changes to the -frontend, you can boot it up as you usually would: +Livepeer Studio comes with a [pkg](https://github.com/vercel/pkg)-bundled +version of the API server and frontend, but does not include a full development +environment for that frontend. If you are making changes to the frontend, you +can boot it up as you usually would: ``` cd studio/packages/www diff --git a/self-hosting/overview.mdx b/self-hosting/overview.mdx index a2fa92b4..0a193d0f 100644 --- a/self-hosting/overview.mdx +++ b/self-hosting/overview.mdx @@ -3,35 +3,30 @@ title: Overview icon: flask --- -Livepeer Studio is powered by Catalyst, the Livepeer network's first -open-source, decentralized media server. Learn how to self-host Catalyst using a -single Docker command and get the full-stack Livepeer Studio experience running -on your laptop. +Learn how to self-host Livepeer Studio using a single Docker command. - **Self-hosted Catalyst is in Alpha**, but we're excited for the first group of - hackers to start working on it! + **Self-hosting is in Alpha**, but we're excited for the first group of hackers + to start working on it! ### Current capabilities: - Boots up a full-stack Livepeer Studio experience with a single command, either locally or on a hosted server. -- Capable of transcoding on the Livepeer mainnet. -- Facilitates easy development of various components of the Livepeer stack. +- Capable of transcoding on the Livepeer Network. - Allows for development of applications against the Livepeer Studio API locally that can then transfer to the hosted version at [livepeer.studio](https://livepeer.studio) when you're ready to go to production. -- Bundles a fully-local offchain go-livepeer gateway and orchestrator, so that - you may test transcoding with no external dependencies. +- Bundles a fully-local offchain Livepeer gateway and orchestrator, so that you + may test transcoding with no external dependencies. ### Current limitations: - No usage or billing data. - No GPU transcoding support. We recommend using very low-bitrate test files, - especially if running the box using Docker for Mac or Docker for Windows. The - built-in profiles for livestream transcoding use a single 240p low-quality - rendition. -- It is currently required to run the node as a Docker image. A single-binary - fully-static build is in the works. + especially if using Docker for Mac or Docker for Windows. The built-in + profiles for livestream transcoding use a single 240p low-quality rendition. +- It is currently required to run Livepeer Studio as a Docker image. A + single-binary fully-static build is in the works.