Hosting and deployment

Share via

Deploy your Hinode site to popular hosting providers.

As a static website, your Hinode site can be deployed virtually anywhere. Hugo provides a comprehensive overview of the more popular deployment solutions  . Hinode uses a different build process compared to a default Hugo site. Review the considerations for more details. The next paragraphs highlight the specific build and deployment process of Hinode for a few selected hosting providers.


Before deciding on your hosting and deployment approach, review the following considerations.

  1. Include npm in your build process

    Hinode supports npm to automate the build process. Visit the Hinode introduction and commands overview for more details.

  2. Configure the build timeout

    You might encounter timeout errors when you generate a large site that contains many resources (such as images). Adjust the timout in config/_default/hugo.toml as needed.

    timeout = "180s"
  3. Consider using build automation

    Many popular Git providers provide the option to automate the build and deployment process ( CI/CD ). You can trigger this process on each release to your main repository branch, or set up a preview during a Pull Request. The examples on this page assume you have a Git repository with GitHub.

  4. Understand the support for custom domain names

    Most hosting providers provide a subdomain, such as <username>, to access your website by default. Usually you have the ability to use a custom domain instead, although additional services and configuration might be needed.

  5. Decide on multiregion and CDN support

    Websites that serve a global audience might benefit from a multiregion or edge deployment to increase availability and reduce latency. You can also consider adding a dedicated CDN , which has the ability to reduce the impact of DDoS attacks for example.

  6. Consider using custom HTTP headers

    Hinode uses custom HTTP headers to enable the Content Security Policy. The support for custom HTTP headers varies per provider, and might need additional services and configuration.

The table below gives a brief overview of the features supported by a few selected hosting providers. The next paragraphs describe the build and deployment process for each provider in more detail.

FeatureAzure blob storageNetlify
AutomationCustom action
Custom domain nameRequires Azure CDN
CDN / Edge networkRequires Azure CDN
HTTP headersRequires Azure CDN

Host on Azure blob storage

Azure supports hosting a static website directly from its blob storage. The service is available for free  for the first 12 months (conditions apply). The next sections describe how to configure the cloud storage correctly and how to deploy your website from your local computer to Azure.


  • You have a Hinode website you are ready to deploy.
  • You do not already have a Azure storage account.


The configuration folder should include a file config/production/deployment.toml. If not, copy it from the Hinode main repository  . The deployment file contains the settings used by the command hugo deploy. The panel below shows the default deployment settings for Azure blob storage. A more detailed example is available on the Hugo website  .

# By default, files are uploaded in an arbitrary order.
# Files that match the regular expressions in the "Order" list
# will be uploaded first, in the listed order.
order = [".webp$", ".jpg$", ".gif$"]

name = "hinode"
URL = "azblob://$web"

# Cache static assets for 1 year.
pattern = "^.+\\.(js|css|svg|ttf)$"
cacheControl = "max-age=31536000, no-transform, public"
gzip = true

pattern = "^.+\\.(png|jpg|webp)$"
cacheControl = "max-age=31536000, no-transform, public"
gzip = false

# Set custom content type for /sitemap.xml
pattern = "^sitemap\\.xml$"
contentType = "application/xml"
gzip = true

pattern = "^.+\\.(html|xml|json)$"
gzip = true

Configure your site

Deploy your site to Azure blob storage in six steps.

If not done so already, sign up for an account on the Azure website  . Log in to the Azure portal and create a storage account. The storage account needs to have a unique name across Azure. Select a region that best fits your needs. Leave all other options to their default value.

Go to the menu section Data management and select Static website. Set the toggle for Static website to Enabled. Azure will then create a storage container $web within your storage account to host your website. Capture the primary endpoint, for example Set the Index document name to index.html. Hit the Save button when done.

Go to the menu section Security + networking and select Access keys. Capture the storage account name, e.g. gethinode. Next, copy either of the two keys to your clipboard. Set the credentials on your local computer:

export AZURE_STORAGE_ACCOUNT="{account name}"
export AZURE_STORAGE_KEY="{storage key}"

Run the following command to build your website locally:

Deploy the files to your Azure blob storage using the folling command. Add --dryRun to review the upload before actually publishing the files.

hugo deploy

Once the deployment has finished, visit the end point captured in step 2 to test the website in your browser.

You can make your static website available via a custom domain. Visit the Azure documentation  on how to map a custom domain to your blob storage endpoint. The static website does not support configuration of HTTP headers. Use Azure CDN to configure HTTP headers  for your static website instead. Review the server configuration to identify the recommended configuration of the Content Security Policy.

Host on Netlify

Netlify can host your website with continous deployment from your Git provider. The starter price plan is free for any public repository and provides 100 GB bandwidth and 300 build minutes each month. Review the next sections how to automatically deploy your site to Netlify on each update to the main branch of your repository.


  • You have an account and repository with GitHub, GitLab, or Bitbucket.
  • You have a Hinode website you are ready to deploy.
  • You do not already have a Netlify account.


The repository root should include a file netlify.toml. If not, copy it from the Hinode main repository  . The configuration file contains the build settings that Netlify will pick up when connecting to your repository. The panel below shows the default build settings. The key command to observe is npm run build, which ensures the site is built properly.

    publish = "exampleSite/public"
    command = "npm run build:example"

    DART_SASS_VERSION = "1.66.1"
    HUGO_VERSION = "0.118.2"
    HUGO_ENV = "production"
    NODE_VERSION = "18.17.1"
    NPM_VERSION = "9.6.7"

The same file also configures several optional plugins. Keep these plugins if you would like to support Dart Sass , use caching, and generate a Lighthouse report upon each build.

    package = "@gethinode/netlify-plugin-dartsass"

    package = "netlify-plugin-hugo-cache-resources"
	# Redirected in exampleSite/config/_default/hugo.toml
	# srcdir = ""

    package = "@netlify/plugin-lighthouse"
    # [plugins.inputs]
    # output_path = "reports/lighthouse.html"

Configure your site

Sign up for Netlify and configure your site in seven steps.

Go to  and click on the button Sign up. Select your preferred signup method next. This will likely be a hosted Git provider, although you also have the option to sign up with an email address. The next steps use GitHub, but other Git providers will follow a similar process.

Enter the credentials for your Git provider and click the button to sign in.

Assuming you have enabled two-factor authentication with your Git provider, authenticate the sign in next. This example uses the GitHub Mobile app.

Click on the button Add new site to set up a new site with Netlify.

Connect to your Git provider to import your existing Hinode repository.

Pick a repository from your Git provider. Ensure Netlify has access to the correct repository.

Review the basic build settings. Netlify will use the settings provided in the preparations. Click on the button Deploy site to start the build and deployment process.

Your site is now ready to be used. Click on the domain settings of your site within the Site overview page to provide a domain alias and to edit the site name as needed. The same section also allows the configuration of a custom domain. Be sure to review your server configuration if you encounter any rendering issues, such as broken links or garbled stylesheets.

Last updated: September 6, 2023 • Add plugin config (3bc02e8)