n nesly
Menu
TR Sign in

Deploy Jekyll

How nesly detects, builds and serves a Jekyll project — and the two commands that put it on a live URL.

Deploy Jekyll on nesly

A Jekyll project is built once and served as static files — no server process to keep alive.

cd your-project
nesly deploy --yes

The first deploy creates the project and prints the live URL; after that, nesly deploy is enough.

How detection sees it

  • A _config.yml is detected as Jekyll. With a Gemfile the build runs bundle install and bundle exec jekyll build — your pinned plugins and theme. Without one, a stock Jekyll builds the site.
  • _site/ is served as static files.

When detection is not what you want, say it yourself: build and start commands, root directory and output directory live in nesly.toml committed next to the code — see builds.

Worth knowing

  • Builds run on Linux: if your Gemfile.lock was created on macOS, run `bundle lock --add-platform x86_64-linux` and commit it, or bundle install will refuse.
  • GitHub Pages-only gems (github-pages) drag in an old Jekyll; pin jekyll directly unless you need that exact environment.
  • When a deploy fails, nesly diagnose reads the logs for you and names the fix.

Full walkthrough: get started. Custom domains, backups, GitHub deploys and the rest of the reference: nesly CLI.