Basic support for audio/video content#372
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds basic support for "seekable" content such as audio and video.
The following snippets serve as a guide for testing video in operation. Video and audio files are served from the configured "assets" location. Configure your CDN instance using the below settings:
Configure CDN
config/config.development.json
Add files to be served
Add an image called "poster.jpg" to the "images" directory, and a video called "video.mp4" to the "assets" directory:
Create the HTML page to serve video content
The following example uses video.js to load and play the video content. The example assumes your CDN is running on
http://localhost:3000, so make adjustments to the HTML where necessary:index.html
Close #371 , #338