Deploy the Static Cache + Videoteca Player template

The Static Cache + Videoteca Player template deploys an application that caches static and dynamic content by file extension, and serves Videofront’s Videoteca player through an iframe. The deployment creates a GitHub repository with the project, an application carrying several cache settings and a preconfigured route that runs the Videoteca Player function, and a domain that serves it.

Every push to that repository is deployed automatically.

Requirements

A GitHub account, to connect with Azion and create the repository.
The Videoteca Player integration installed and configured. Refer to Videofront Player.
A Videoteca account, which carries the username and the API token the form asks for.
The template uses Application Accelerator, Functions, Image Processor, and Cache, which can generate usage-related costs. For the rates, refer to Pricing.
Access to Azion Console. Refer to Access Azion Console.

Deploy the template

Select the button below to open the template in Azion Console:

Deploy

Configure the template fields

The configuration form requests the information the application needs. An asterisk marks a mandatory field.

First, name the application. The storage bucket and the function take the same name, so it must be unique; a name already in use returns an error message.

Then complete the fields of the Videoteca Player integration:

Field	What to enter
Origin Address	The domain name or the IP address of the origin.
Custom Host Header	The value of the `host` header sent to the origin. Left blank, it takes the origin address. For more information, refer to Host Header.
Videoteca Player Path	The path that serves the player. For example: `/player`.
Videoteca Username	The username of your Videoteca account.
Videoteca API Token	The API token of your Videoteca account.

The API token is available at https://<YOUR-USER>.videotecaead.com.br/Apidoc, where <YOUR-USER> is your Videoteca username.

Select Deploy to start the deployment. A window shows the logs while it runs, and the page then shows the application information and the options to continue.

The configuration takes time to propagate across Azion’s distributed infrastructure. Wait a few minutes for the URL to answer.

Manage the template

Every setting the form asked for stays editable in Azion Console. To open the application:

Access Applications

Access Azion Console > Products Menu > Applications.

Find the application

Find the application the template created. The list is alphabetical, and the search bar filters it by Application Name only.

Select the application

Select the application to open its settings.

The application page carries the cache settings and the route the template configured.

To change how long the static files stay cached, refer to Create a cache setting. For the fields of an application, refer to Applications quickstart.

Add a custom domain

The deployed application answers on a domain Azion assigns to its workload, in the format xxxxxxxxxx.map.azionedge.net. You can serve it on a domain of your own instead.

For more information, refer to Add a custom domain to a workload.