From 627f69a3111c8354c8623cf703d935d3a299ae1e Mon Sep 17 00:00:00 2001 From: ts-klassen Date: Fri, 3 Feb 2023 19:32:03 +0900 Subject: [PATCH 1/2] Changed yoursite[.]com to example[.]com --- player/page.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/player/page.html b/player/page.html index 590d6af..c3b613d 100644 --- a/player/page.html +++ b/player/page.html @@ -9,8 +9,8 @@ - - + + From ef59f22ef20a9ecac9b0f5b851fd5f8cd223920d Mon Sep 17 00:00:00 2001 From: ts-klassen <104614062+ts-klassen@users.noreply.github.com> Date: Fri, 3 Feb 2023 19:45:09 +0900 Subject: [PATCH 2/2] What to do with example.com Signed-off-by: ts-klassen <104614062+ts-klassen@users.noreply.github.com> --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 0e70f78..9904773 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,7 @@ The basic steps to deploy are: - Unzip the contents into a publicly accessible path on your website - Open the `page.html` file and ensure the `twitter:image`, `twitter:player` and `twitter:player:stream` values point to your server and file locations - Update the content (`container.html`) that you're pointing to... don't use the sample video, please! +- Change ```example.com``` on ```player/page.html``` to your domain - Ensure all paths are specified as secure (https://) - Test your URL