Netlify
Updated May 16, 2026
Netlify reads a small netlify.toml at your project root to pick up the build command and publish directory. The rest — Git previews, atomic deploys, custom domains — is handled automatically.
Build the site
livemark buildOutput lands in .livemark/build/client/.
Configure netlify.toml
[build]
command = "livemark build"
publish = ".livemark/build/client"That's all Netlify needs. The same file unlocks netlify dev locally if you ever want to mirror the platform's edge behavior.
Deploy with the git integration
The recommended path: connect your repo at app.netlify.com/start. Netlify reads netlify.toml, runs the build, and ships every push to main to production. Other branches and PRs get unique deploy preview URLs automatically.
Deploy with the CLI
For one-shot or scripted deploys:
livemark build
netlify deploy --prod --dir=.livemark/build/clientThe first run prompts for netlify login and links the directory to a site.
Deploy with GitHub Actions
Netlify's git integration is usually enough, but a workflow gives you test-before-deploy gating:
name: deploy
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: pnpm/action-setup@v4
- uses: actions/setup-node@v4
with:
cache: pnpm
node-version: 24
- run: pnpm install
- run: pnpm test
- run: livemark build
- uses: nwtgck/actions-netlify@v3
with:
publish-dir: .livemark/build/client
production-deploy: true
env:
NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}Get the auth token from User settings → Applications → Personal access tokens, and the site ID from Site settings → General.
Custom domain
In the site dashboard, Domain management → Add a domain. Netlify provisions DNS and a certificate. Set the same domain as site in livemark.config.ts.
See also
- Site Metadata —
sitepopulates the sitemap and RSS feed URLs. - Deployment — back to the host index.
Created with ❤ and Livemark