Name: dlss-wowza
Owner: Stanford University Digital Library
Description: Wowza server side modules.
Created: 2016-05-02 17:53:19.0
Updated: 2016-05-02 21:42:14.0
Pushed: 2016-12-16 13:04:34.0
Homepage: null
Size: 68086
Language: Java
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Wowza server side modules. Uses Gradle (with the Gradle wrapper) as the build tool (akin to Ruby's rake).
./gradlew build
Before running this command, you'll need to set these environment variables:
WOWZA_HONEYBADGER_API_KEY
: You can get the API key from our Honeybadger project (DLSS-Wowza
). Note that you may need to get added to the DLSS-Wowza
project as a user in order to obtain the key (someone from Devops should be able to add you).WOWZA_HONEYBADGER_ENV
: Anything other than the names of the deployed environments should be fine. E.g., something like dlss_wowza_laptop_$USER
.If the environment variables are not set, your tests will fail.
In the Wowza GUI interface, select your Wowza Application, and click on the modules tab. Add a module with the class name edu.stanford.dlss.wowza.SulWowza
(the name and description are arbitrary strings).
Alternatively, you can manually edit Application.xml and then reload the Wowza application. The <Modules>
element in Application.xml
should include something like this:
odule>
<Name>SulWowza</Name>
<Description>SUL Authorization against Stacks</Description>
<Class>edu.stanford.dlss.wowza.SulWowza</Class>
Module>
You can configure the SulWowza plugin using Wowza's GUI interface, but you will also need to add some properties.The three properties our SulWowza plugin uses are:
You can add these properties using the Wowza GUI interface: select your Wowza application, click on the properties tab; scroll to the bottom for custom properties and add them.
Alternatively, you can manually edit Application.xml and then reload the Wowza application. The <Properties>
element in Application.xml
should include something like this:
roperty>
<!-- stacks token verification baseURL -->
<Name>stacksURL</Name>
<Value>https://stacks-test.stanford.edu</Value>
Property>
roperty>
<!-- stacks service connection timeout (time to establish a connection), in seconds; default is 30 -->
<Name>stacksConnectionTimeout</Name>
<Value>20</Value>
<Type>Integer</Type>
Property>
roperty>
<!-- stacks service connection timeout (time for reading stream after connection is established),
in seconds; default is 30 -->
<Name>stacksReadTimeout</Name>
<Value>20</Value>
<Type>Integer</Type>
Property>
conf/version
. This should be just the version number itself, e.g. 1.7.1
or 2.0.0-beta
.v
prefix, e.g. v1.7.1
or v2.0.0-beta
(corresponding with the conf/version
example).deploymentJar
gradle task (a la Jenkins), the git tag (e.g v1.7.1
) must match the contents of conf/version
(e.g. 1.7.1
) other than the leading v, present only in the git tag.wowza-auth-plugin
) that creates the versioned .jar artifact for deployment../gradlew deploymentJar
or ./gradlew deploymentJarRelaxed
(the latter is needed if conf/version
doesn't match the head commit in the current branch)./gradlew tasks
./gradlew –help
c -d classes -cp .:libs/wms-restlet-2.2.2.jar:libs/wms-server.jar:libs/wms-httpstreamer-cupertinostreaming.jar:libs/wms-httpstreamer-mpegdashstreaming.jar:libs/log4j-1.2.17.jar:libs/junit.jar src/edu/stanford/dlss/wowza/SulWowza.java src/edu/stanford/dlss/wowza/SulWowzaTester.java
cf dlss-wowza.jar classes/edu/stanford/dlss/wowza/SulWowza* conf