---
name: azion-deploy-the-static-cache-videoteca-player-template
description: >-
  Deploy an application that caches static files by extension and serves the Videoteca player through a preconfigured route.
---

# 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](https://github.com/signup) account, to connect with Azion and create the repository.
- The Videoteca Player integration installed and configured. Refer to [Videofront Player](/en/documentation/guides/media-and-streaming/streaming/videofront-player/).
- A Videoteca account, which carries the username and the API token the form asks for.
- The template uses [Application Accelerator](/en/documentation/platform/applications/#application-accelerator), [Functions](/en/documentation/platform/functions/), [Image Processor](/en/documentation/platform/applications/#image-processor), and [Cache](/en/documentation/platform/applications/#cache), which can generate usage-related costs. For the rates, refer to [Pricing](/en/documentation/fundamentals/pricing/).
- Access to Azion Console. Refer to [Access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).

---

## Deploy the template

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

[Deploy](https://console.azion.com/create/videofront/static-cache-videoteca-player)

---

## 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](/en/documentation/platform/connectors/origins/#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.

> **Note**
>
> 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:

1. **Access Applications**

   Access [Azion Console](https://console.azion.com/) > **Products Menu** > **Applications**.

2. **Find the application**

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

3. **Select the application**

   Select the application to open its settings.

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

> **Tip**
>
> To change how long the static files stay cached, refer to [Create a cache setting](/en/documentation/guides/application-performance/cache-and-purge/tune-cache-settings/). For the fields of an application, refer to [Applications quickstart](/en/documentation/platform/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](/en/documentation/guides/platform/migration/configure-a-domain/).