pagehaus

Preview, check and deploy plain HTML websites from the command line.

pagehaus serve [folder]     preview the site at http://localhost:8080, with Server Side Includes,
                            reloading the page when you save a file
pagehaus check [folder]     find broken links, missing files, links whose case doesn't match the file,
                            files too big, pages without a title or description, mistakes in includes
                            and _redirects
pagehaus login              save an API token for deploy
pagehaus deploy [folder]    upload the folder to your Pagehaus site

Checking a site

$ pagehaus check
Checked /Users/sam/bakery: 5 pages, 7 files.

problem: links to /contact.html, which doesn't exist.
         in about.html, blog/first.html, blog/second.html and 1 more
problem: links to /img/team.jpg, but the file is named img/Team.JPG. That works on Windows and Mac, not on a web server: the case must match.
         in about.html, blog/first.html, blog/second.html and 1 more
problem: menu.html: links to file:///C:/Users/sam/Desktop/menu.pdf, which is on your computer: visitors can't reach it.
warning: menu.html: no <title>: search results and browser tabs show the address instead.

3 problems, 1 warning.

Pages are checked with their Server Side Includes filled in, so a broken link in a shared header is reported once, with the pages it's on. File names are compared exactly, as a web server does, even on a Mac or Windows disk that doesn't mind the case. The exit status is 1 when there are problems (with --strict, warnings too), so check can stop a CI build. It works on any static site, not only Pagehaus ones.

Install

• Homebrew (macOS, Linux): brew install pagehaus/tap/pagehaus
• With .NET: dotnet tool install -g pagehaus
• Or download the file for your computer from the latest release (Windows, macOS, Linux; no .NET needed), unpack it and put pagehaus on your PATH. On macOS or Linux:

  curl -L https://github.com/pagehaus/cli/releases/latest/download/pagehaus-osx-arm64.tar.gz | tar -xz pagehaus
  

  (osx-x64 for Intel Macs, linux-x64 or linux-arm64 for Linux.)

Deploying to Pagehaus

$ pagehaus login
Make an API token at https://pagehaus.app/account/api (for Access, choose "yoursite: read and write"), then paste it here.
Token:
Logged in with "laptop" (site bakery, can deploy).

$ pagehaus deploy --dry-run
Checking what would change on bakery: 12 files, 84.2 KB zipped...
  2 new (would be written): /menu.html, /img/croissant.jpg
  10 replaced (would be written): /index.html, /style.css, ...
Dry run: nothing was changed. Run without --dry-run to deploy.

$ pagehaus deploy

deploy runs check first and stops if it finds problems (--force deploys anyway). It uploads every file except hidden ones (.git, .env...); files you deleted locally stay on the site, so delete those in the dashboard. With several sites, say which: --site bakery. In CI, set PAGEHAUS_TOKEN instead of logging in. On GitHub, the Deploy to Pagehaus action does it all in three lines. The saved token is in ~/.config/pagehaus/config.json (%APPDATA%\pagehaus\config.json on Windows), readable only by you.

Server Side Includes

serve processes Server Side Includes the way Apache's mod_include does: include, echo, set, config, flastmod, fsize and if/elif/else/endif (no exec), with limits that keep untrusted pages safe. It's the same engine Pagehaus hosting uses, so what you see is what you get there. The engine is also a .NET library: src/Pagehaus.Ssi.

Conditions use Apache's long-standing expression syntax ($NAME = value, !=, /regex/, &&, ||, !), which is enough for the classic use, a shared menu that marks the page you're on:

<a href="/about.html"<!--#if expr="$DOCUMENT_URI = /about.html" --> aria-current="page"<!--#endif -->>About</a>

check reports conditions that don't close, expressions it can't read, and missing files in any branch, including ones the pages checked never show.

Pagehaus adds one directive of its own: <!--#counter -->, a visitor counter, as plain text or as digits in boxes (theme="classic", "odometer", "led") in your site's colours. serve shows a sample number; the real one is counted online.

Redirects

A _redirects file at the top of the site sends old addresses to new ones, in the format Netlify and Cloudflare Pages use: one rule per line, /old-page /new-page.html (301 unless it ends in 302), with /blog/* /posts/:splat and /news/:year/:slug for patterns. A rule only applies where nothing else is found, so it never hides a file. serve follows the rules as Pagehaus does, and check reports lines it can't read, redirects that go round in a circle, and doesn't count links a rule covers as broken. See Redirects.

Building

Needs the .NET 10 SDK. dotnet test, then dotnet run --project src/Pagehaus.Cli -- serve path/to/site.

MIT licence. Made by Pagehaus, plain HTML hosting.