// the find
benbalter/jekyll-auth
A simple way to use GitHub OAuth to serve a protected Jekyll site to your GitHub organization
Jekyll Auth wraps a Jekyll site in a Sinatra app and gates access behind GitHub OAuth, letting you restrict a static site to members of a GitHub org. It runs on Heroku, using the `rake assets:precompile` hook to build Jekyll on deploy. The repo itself says it's end of life.
The core idea is clean: Sinatra as a thin auth proxy over a static `_site` folder is minimal and easy to reason about. The `sinatra_auth_github` dependency does the OAuth heavy lifting correctly. Team/org-level access control is a single config value rather than a user list. The getting-started docs are thorough for the era they were written.
The project is explicitly marked end of life by the author — the README's first section says so. It's Heroku-specific in its setup instructions and relies on Heroku's `rake assets:precompile` hook, which is a brittle coupling. Travis CI badges point to a CI service that's effectively dead for open source. There's no path forward to non-org access patterns (individual users, teams within an org) without forking it yourself.