netlify

Use the netlify CLI to create projects (“sites”), link local folders, and configure CI/CD from GitHub.

Pre-reqs

• - INLINECODE1
• Logged in (netlify login) or provide --auth $NETLIFY_AUTH_TOKEN.
• Know the Netlify team/account slug you want to create sites under (optional but recommended).

Helpful checks:

CODEBLOCK0

Monorepo pattern (recommended)

For one repo with multiple sites (e.g. sites/seattlecustomboatparts.com, sites/floridacustomerboatparts.com):

• - Create one Netlify site per domain.
• Set the site’s Base directory to that subfolder.
• Put a netlify.toml inside that subfolder.

This keeps each domain’s build config self-contained.

Hugo subfolder netlify.toml

Create sites/<domain>/netlify.toml:

CODEBLOCK1

(Adjust HUGO_VERSION as needed.)

Fast workflow: create + link + init CI/CD

1) Create a Netlify site (project)

CODEBLOCK2

Notes:

• - --with-ci starts CI hooks setup.
• If you need manual control, add --manual.

2) Link local folder to the created site

CODEBLOCK3

3) Connect to GitHub for continuous deployment

CODEBLOCK4

This is usually interactive (select Git remote/repo + build settings). For automation we can pre-create netlify.toml and then accept defaults.

Environment variables

Set per-site vars:

CODEBLOCK5

Useful for monorepos:

• - CONTACT_EMAIL (or other shared config)

Deploy

Manual deploys (handy for quick preview):

CODEBLOCK6

Included scripts

• - scripts/hugo_netlify_toml.sh: create a netlify.toml in a Hugo subfolder
• INLINECODE15: helper to create/link/init a site for a subfolder

When using scripts, prefer passing NETLIFY_AUTH_TOKEN via env for non-interactive runs.