![wowza streaming engine archive livestream in subdirectory wowza streaming engine archive livestream in subdirectory](https://ml6ipigidljb.i.optimole.com/wF9Nep4-WBBnSyAw/w:auto/h:auto/q:75/wm:106380:0.5:sowe:0:0:0.05/https://www.broadcastbruce.com/wp-content/uploads/2017/09/Wowza-is-Flexible.png)
wowza-jre-9/įor the curious: If you’d like to know which version of Java your installation of WSE is currently running on, you can retrieve that information easily using Docker. wowza-jre-9/ curl \ | tar -jx -strip-components=1 -C.
WOWZA STREAMING ENGINE ARCHIVE LIVESTREAM IN SUBDIRECTORY DOWNLOAD
Let’s download and unzip the custom JRE and then place it in a directory inside our project folder: mkdir -p. This version will contain the appropriate files for Linux, macOS, and Windows.įor this tutorial, we are going to use the Linux version. Therefore we have to change Eclipse’s compiler settings and instead link to a version of the Java JRE which is supported by WSE.įortunately, Wowza offers a custom packaged version of OpenJDK Java SE JRE 9.0.4. This means our custom WSE module will compile in Eclipse, but it will not run in WSE. However, WSE v4.7.8 and later requires OpenJDK Java SE JRE 9.0.4 at a minimum but supports up to Java version 12. docker rm -f wowza Download custom JRE versionĪt the time of this writing, Eclipse IDE comes with Java 16 installed. docker cp wowza:/usr/local/WowzaStreamingEngine/lib/. docker cp wowza:/usr/local/WowzaStreamingEngine/content/. docker cp wowza:/usr/local/WowzaStreamingEngine/conf/. Wowza provides some configuration options to refine our setup later.īefore starting our container setup, we need to copy the required files from inside the WSE container.Ĭreate a temporary container, copy the required folder and files to our project folder, then delete the temporary container: docker create -it -name wowza wowzamedia/wowza-streaming-engine-linux:latest bash docker cp wowza:/usr/local/WowzaStreamingEngine/applications/. lib:/usr/local/WowzaStreamingEngine/lib:ro networks : - public networks : public : content:/usr/local/WowzaStreamingEngine/content. conf:/usr/local/WowzaStreamingEngine/conf. applications:/usr/local/WowzaStreamingEngine/applications. Inside the folder, create a file named docker-compose.yml and use the following configuration as a starter: services : application : container_name : wowza image : wowzamedia/wowza-streaming-engine-linux:latest entrypoint : /sbin/entrypoint.sh restart : unless-stopped ports : - "8000:80" # RTMP streaming fallback - "443:443" # RTMPS streaming - "1935:1935" # RTMP and HLS streaming - "8086-8088:8086-8088" # Administration - "8089:8089" # REST API documentation server - "8090:8090" # HTTPS for Wowza Streaming Engine Manager (web interface) volumes :. Let’s get started:įirst, create a local project folder and switch to it: mkdir -p wowza-module-dev cd wowza-module-dev To make our lives easier we are going to use Docker Compose to run our Docker container locally. Also, to preserve our Wowza application state, we are going to bind-mount three more subfolders: applications, conf, and content. However, we are going to need those Java libraries to compile our module. You probably would not want to do this in production since the content of that folder changes with updates to Wowza Streaming Engine. ?♂️įor this setup, we are going to bind-mount the lib subdirectory from /usr/local/WowzaStreamingEngine/ to our host filesystem.
![wowza streaming engine archive livestream in subdirectory wowza streaming engine archive livestream in subdirectory](https://www.wowza.com/uploads/blog/ConfigureSourceSecurity_1.png)
I contacted their customer support about this but did not receive a satisfactory reason why. That said, Wowza’s official Docker image is updated rather infrequently. Also, using bind-mounts / Docker volumes you can more easily separate your custom config from the rest of the installation and track your changes in source control systems. I find installing a newer version much easier than in-place updating an already installed version. I prefer running Wowza Streaming Engine inside Docker, mainly because of maintenance reasons. If you already have an instance of Wowza Streaming Engine running, you can use that one instead. Setup Wowza Streaming engine locally using Docker Create a basic Wowza Streaming Engine Java module for a Linux runtime.Setup Wowza Streaming Engine (WSE) locally using Docker.If not, you might need to adapt some of the commands provided. Also, I assume you are following this tutorial on a machine running a recent version of macOS. In this post, I intend to share my journey to hopefully make it easier for others. ⚠️ Disclaimer: I am not a Java developer so the language, the tooling, all of it was new to me. Hello everyone and boy, have I been struggling with building a custom module for Wowza Streaming Engine. “Why is this not working?” shouted the angry developer at his innocent screen.
![wowza streaming engine archive livestream in subdirectory wowza streaming engine archive livestream in subdirectory](https://ml6ipigidljb.i.optimole.com/wF9Nep4-tSiwcPlM/w:auto/h:auto/q:75/wm:106380:0.5:sowe:0:0:0.05/https://www.broadcastbruce.com/wp-content/uploads/2017/09/Wowza-Streaming-Engine-End-to-End.png)
Then, customize compiler settings by installing and linking a compatible Java JRE version. Follow Wowza’s official instructions to set up Eclipse.