The Static Website template creates an infrastructure as code project in your favorite language that deploys an HTML website to Microsoft Azure with Pulumi. It uses an Azure Blob Storage account for file storage, configures the storage account to host a website, and deploys an Azure CDN Endpoint to serve the website with low latency, caching, and HTTPS. The template generates a complete Pulumi program, including placeholder web content, to give you a working project out of the box that you can customize easily and extend to suit your needs.
Using this template
$ mkdir my-site && cd my-site $ pulumi new static-website-azure-typescript
$ mkdir my-site && cd my-site $ pulumi new static-website-azure-python
$ mkdir my-site && cd my-site $ pulumi new static-website-azure-go
$ mkdir my-site && cd my-site $ pulumi new static-website-azure-csharp
$ mkdir my-site && cd my-site $ pulumi new static-website-azure-yaml
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a finished that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in
Deploying the project
The template requires no additional configuration. Once the new project is created, you can deploy it immediately with
$ pulumi up
When the deployment completes, Pulumi exports the following stack output values:
- The provider-assigned hostname of the Azure Blob Storage container.
- The fully-qualified HTTP URL of the storage container endpoint.
- The provider-assigned hostname of the Azure CDN. Useful for creating
CNAMErecords to associate custom domains.
- The fully-qualified HTTPS URL of the Azure CDN.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed
cdnURL, for example, can be used from the command line to open the newly deployed website in your favorite web browser:
$ open $(pulumi stack output cdnURL)
Customizing the project
Projects created with the Static Website template expose the following configuration settings:
- 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.
- The file to use for top-level pages. Defaults to
- The file to use for error pages. Defaults to
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 as shown below.
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
$ pulumi config set path ../my-existing-website/build $ pulumi up
You can cleanly destroy the stack and all of its infrastructure with
$ pulumi destroy
Congratulations! You’re now well on your way to managing a production-grade static website on Microsoft Azure with Pulumi — and there’s lots more you can do from here: