Jekyll and Bridgetown
How Gigadrive Network builds a Jekyll or Bridgetown site and serves it from the edge.
Jekyll and Bridgetown sites are built once and served as static files, with no Function.
Jekyll
Gigadrive Network detects Jekyll when your Gemfile.lock, or your Gemfile without a lockfile, lists jekyll or github-pages. The build installs your gems with Bundler, then runs jekyll build with JEKYLL_ENV=production, and every file in _site is published to the edge.
Bridgetown
Gigadrive Network detects Bridgetown when your lockfile lists bridgetown. The build installs your gems, then runs bridgetown deploy with BRIDGETOWN_ENV=production, which also builds the site's front end with Node.js, and every file in output is published to the edge.
The Ruby version
The build runs on the Ruby version your project names in .ruby-version, .tool-versions, the ruby line in your Gemfile or the RUBY VERSION in Gemfile.lock, and on Ruby 3.4 when it names none. Native gems such as sassc are compiled during the build, so no Ruby runs once the site is published.
A site that needs redirects, headers or a custom 404 page configures them as for any static site.