Category: Deployment

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 …

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 …

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 …

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 …

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 …