Build with Hexo
Deploy a Hexo site to an Azion domain from the Hexo Boilerplate template, a GitHub repository, or the Azion CLI.
You can put a Hexo site on Azion three ways: deploy the Hexo template from Azion Console, import your own repository from GitHub, or run the Azion CLI. Each route leaves the site live on an Azion domain.
Azion serves a Hexo site as a static application. The Hexo build generates the site in ./public, and the deploy copies that folder to a storage bucket behind an application. To see which other frameworks Azion builds, refer to Frameworks compatibility.
Prerequisites
Console
- An Azion account. To create one, refer to Create an account.
- Access to Azion Console. To sign in, refer to How to access Azion Console.
- A GitHub account. The template form connects it during the deploy when it asks for one.
Hexo templates
The Console route deploys a template, a Hexo project that is ready to build. It starts from this template:
| Template | Use |
|---|---|
| Hexo Boilerplate | Single-page application |
Hexo Boilerplate has a guide of its own, linked in the table. For the template catalog, refer to Azion Marketplace. In the CLI route, the azion init template picker of the Hexo preset lists Hexo Boilerplate as its only entry.
Deploy the site
Every route builds the Hexo project and creates the Azion resources that serve it. Follow the panel for your route:
Console
To deploy the Hexo template from Azion Console:
Access Azion Console > Create > Templates.
In Search by name, framework, or keyword, enter Hexo.
If the form shows GitHub Connection, select Connect with GitHub and install the Azion GitHub App.
In Git Scope, select the scope for the template.
While the project builds, the deploy page shows the Deploy Log. A successful deploy shows Successfully created!, the domain URL, and a Manage button that opens the application.
Check the site
Each route gives you the URL of the site’s Azion domain, in the form https://xxxxxxxxxx.map.azionedge.net. In Azion Console, the deploy page shows it; in the CLI route, azion deploy prints it at the end. Open that URL in a browser to load the Hexo site.
The first deploy can take several minutes to answer from every location; later deploys take about two minutes. A location that does not have the site yet answers with a 404 page that reads There's nothing here yet. If you get that page, wait, then load the URL again.