Netlify provides continuous deployment of static sites (example, built using hugo, and provides hosting for those too. The condition is that all site content has to be purely static.. so no scripts running on their server.
Here's a typical flow for deploying sites through Netlify:
- User commits changes to the git repo holding the source of their static site.
- Netlify receive that commit ping, and triggers a fresh build of the user's site using that latest commit.
- Netlify deploys that site at the domain the user configured.
- As Netlify needs the served sites to be 100% static, they cannot run any script (PHP, etc.) to serve as an endpoint for Webmention, micropub, etc.
- Endpoints for such Netlify-hosted sites need to be hosted separately somewhere else.
- TODO: Someone who knows how to get around this limitation needs to update this section with that solution.
However, Netlify does offer a serverless functions platform called Functions which https://piperswe.me/ has written about using for Serverless Indieauth at https://piperswe.me/posts/serverless-indieauth/
- jekyll-netlify-headers - Ruby gem for generating a Netlify headers configuration from a Jekyll configuration
- jekyll-netlify-redirects - Ruby gem for generating a Netlify redirects configuration from a Jekyll configuration
- Kaushal Modi uses GitLab + hugo + Netlify for his homepage.
- Jason Garber uses GitHub, Jekyll, and Netlify for hosting several static websites.
- Ryan Johnson uses GitLab + hugo + Netlify for his homepage.
- Jamie Tanna uses GitLab Hugo and Netlify for www.jvt.me