Deployment on OINK

Deployment on Cloudflare Pages

Mon, 01 Jan 0001 00:00:00 +0000

Cloudflare Pages can build an Oink site from a connected GitHub or GitLab repository and create preview deployments for reviewed branches. The consumer build runs Hugo Extended directly and does not need a frontend package install.

Configure the project

Import the repository in Workers & Pages, select the production branch, and use these settings:

Setting	Value
Production branch	`main`, or the reviewed source branch
Build command	`hugo --gc --minify`
Build output directory	`public`
`HUGO_VERSION`	`0.164.0`
`SKIP_DEPENDENCY_INSTALL`	`1`

Set HUGO_VERSION in both the Production and Preview environments. Cloudflare Pages’ v3 build image currently defaults to Hugo 0.147.7, which is below Oink’s minimum 0.160.1. Pinning the validated version prevents a build-image update from silently changing the toolchain. SKIP_DEPENDENCY_INSTALL=1 disables the generic dependency installation step that an Oink consumer does not use.

Deployment on GitHub Pages

Mon, 01 Jan 0001 00:00:00 +0000

If your source is hosted on GitHub, GitHub Pages can build and publish the site with a single Actions workflow. The consuming site needs Hugo Extended but does not need Node.js, npm, PostCSS, or a generated deployment branch.

Project sites use a URL such as https://<OWNER>.github.io/<REPOSITORY>/; user and organization sites use https://<OWNER>.github.io/. Custom domains are also supported.

Prepare the repository

Push the complete site source to GitHub and confirm that this command succeeds from the repository root:

Other hosts

Mon, 01 Jan 0001 00:00:00 +0000

Netlify can build a site from GitHub, GitLab, or Bitbucket and publish a preview for each pull request. An OINK consumer build runs Hugo Extended directly; it does not install Node.js packages or invoke PostCSS.

Configure the site

Push the complete source to your Git provider, import the repository in Netlify, and use these build settings:

Setting	Value
Build command	`hugo --gc --minify`
Publish directory	`public`
`HUGO_VERSION`	`0.164.0` or another theme-validated version

If Netlify detects package manifests that exist only for theme-maintainer tooling, disable automatic dependency installation for the site. They are not part of the consumer build contract.

Serving your site locally

Mon, 01 Jan 0001 00:00:00 +0000

Depending on your deployment choice you may want to serve your site locally during development to preview content changes. To serve your site locally:

Ensure you have an up to date local copy of your site files cloned from your repo.
Ensure Hugo Extended and any source-fetch tools required by your chosen installation method are installed, as described in Prerequisites and installation. Node.js and PostCSS are not site-build prerequisites.
Run the hugo server command in your site root. By default your site will be available at http://localhost:1313.

Deployment

Mon, 01 Jan 0001 00:00:00 +0000

An OINK site builds to a plain static directory. Anywhere that serves static files can host it — no Node runtime, no server-side rendering, no build plugins.

Production build

BASH

hugo --gc --minify

Output goes to public/, which can be deployed independently of the source tree.

--gc , flag: Cleans unreferenced cache resources after the build.
--minify , flag: Minifies HTML, CSS, JS, and XML output.
--baseURL , string: Overrides the configured baseURL. Must include the path when deploying to a subpath.