Azure Static Website
The Azure Static Website template scaffolds a Pulumi project that stores site files in an Azure Blob Storage account configured for static website hosting and serves them through an Azure CDN Endpoint for low-latency delivery, caching, and HTTPS. The template ships with placeholder web content so the project deploys end to end out of the box.
Using this template#
To use this template to deploy a website of your own, make sure you’ve installed Pulumi and configured your Azure credentials, then create a new project using the template in the language of your choice:
TypeScript
Python
Go
C#
YAML
HCLmkdir my-site && cd my-sitepulumi new static-website-azure-typescriptAlternatively, you can create and configure a new project with this template (static-website-azure-typescript) in Pulumi Cloud.
mkdir my-site && cd my-sitepulumi new static-website-azure-pythonAlternatively, you can create and configure a new project with this template (static-website-azure-python) in Pulumi Cloud.
mkdir my-site && cd my-sitepulumi new static-website-azure-goAlternatively, you can create and configure a new project with this template (static-website-azure-go) in Pulumi Cloud.
mkdir my-site && cd my-sitepulumi new static-website-azure-csharpAlternatively, you can create and configure a new project with this template (static-website-azure-csharp) in Pulumi Cloud.
mkdir my-site && cd my-sitepulumi new static-website-azure-yamlAlternatively, you can create and configure a new project with this template (static-website-azure-yaml) in Pulumi Cloud.
mkdir my-site && cd my-sitepulumi new static-website-azure-hclAlternatively, you can create and configure a new project with this template (static-website-azure-hcl) in Pulumi Cloud.
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a finished project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in index.tsindex.js__main__.pymain.goProgram.csProgram.fsProgram.vbApp.javaPulumi.yaml for a closer look.
Deploying the project#
The template requires no additional configuration. Once the new project is created, you can deploy it immediately with pulumi up:
pulumi upWhen the deployment completes, Pulumi exports the following stack output values:
- originHostname
The provider-assigned hostname of the Azure Blob Storage container.
- originURL
The fully-qualified HTTP URL of the storage container endpoint.
- cdnHostname
The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.- cdnURL
The fully-qualified HTTPS URL of the Azure CDN.
- originHostname
The provider-assigned hostname of the Azure Blob Storage container.
- originURL
The fully-qualified HTTP URL of the storage container endpoint.
- cdnHostname
The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.- cdnURL
The fully-qualified HTTPS URL of the Azure CDN.
- originHostname
The provider-assigned hostname of the Azure Blob Storage container.
- originURL
The fully-qualified HTTP URL of the storage container endpoint.
- cdnHostname
The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.- cdnURL
The fully-qualified HTTPS URL of the Azure CDN.
- originHostname
The provider-assigned hostname of the Azure Blob Storage container.
- originURL
The fully-qualified HTTP URL of the storage container endpoint.
- cdnHostname
The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.- cdnURL
The fully-qualified HTTPS URL of the Azure CDN.
- originHostname
The provider-assigned hostname of the Azure Blob Storage container.
- originURL
The fully-qualified HTTP URL of the storage container endpoint.
- cdnHostname
The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.- cdnURL
The fully-qualified HTTPS URL of the Azure CDN.
- origin_url
The fully-qualified HTTP URL of the storage container endpoint.
- origin_hostname
The provider-assigned hostname of the Azure Blob Storage container.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed URL of the deployed site, for example, can be used from the command line to open it in your favorite web browser:
open $(pulumi stack output cdnURL)open $(pulumi stack output cdnURL)open $(pulumi stack output cdnURL)open $(pulumi stack output cdnURL)open $(pulumi stack output cdnURL)open $(pulumi stack output origin_url)Customizing the project#
Projects created with the Static Website template expose the following configuration settings:
- path
The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.- indexDocument
The file to use for top-level pages. Defaults to
index.html.- errorDocument
The file to use for error pages. Defaults to
error.html.
- path
The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.- indexDocument
The file to use for top-level pages. Defaults to
index.html.- errorDocument
The file to use for error pages. Defaults to
error.html.
- path
The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.- indexDocument
The file to use for top-level pages. Defaults to
index.html.- errorDocument
The file to use for error pages. Defaults to
error.html.
- path
The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.- indexDocument
The file to use for top-level pages. Defaults to
index.html.- errorDocument
The file to use for error pages. Defaults to
error.html.
- path
The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.- indexDocument
The file to use for top-level pages. Defaults to
index.html.- errorDocument
The file to use for error pages. Defaults to
error.html.
- path
The path to the folder containing the files of the website. Defaults to
./www, which is the name (and relative path) of the folder included with the template.- index_document
The file to use for top-level pages. Defaults to
index.html.- error_document
The file to use for error pages. Defaults to
error.html.
All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with pulumi config set:
Using your own web content#
If you already have a static website you’d like to deploy on Azure with Pulumi, you can do so either by replacing placeholder content in the www folder or by configuring the stack to point to another folder on your computer with the path setting:
pulumi config set path ../my-existing-website/buildpulumi upCleaning up#
You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:
pulumi destroyLearn more#
- Browse other architecture templates in the Templates gallery.
- Explore the Azure Native provider API docs in the Pulumi Registry.
- Walk through Pulumi from the ground up in Pulumi Tutorials.
- Read the latest Azure posts on the Pulumi blog.