Skip to content

Releases

Stoke v2.0.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 23:43
e477d3c
  • On a Mac, sites can use the usual ports 80 and 443: "Use 80 and 443" on the Sites page (admin password once) and they open as http://shop.test, without :8080. A system rule forwards only this computer's own 127.0.0.1 and ::1 to Stoke, and "Stop using 80 and 443" takes it away again
  • Static sites and folders with an index.html answer again: / and /docs/ served 404 because only index.php was looked for
  • On a Mac, the "Move over from Herd" page no longer says Herd isn't installed: it points to stoke import:herd, which brings Herd's sites over
  • The PHP builds for macOS now include mbstring's regular expressions, which Laravel needs (Call to undefined function mb_split()). PHP versions installed before get them by installing again: stoke php:install <version>

Stoke v2.0.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 20:30
5e4cdad

Hearth is now called Stoke: the old name sounded too much like Herd.

  • On its first start, Stoke moves Hearth over by itself: it stops Hearth, moves ~/.config/hearth to ~/.config/stoke with every PHP and Node version, service, site, setting and the trusted certificate authority, and leaves a link at the old path so tools that still point there keep working
  • The terminal PATH, Claude's and Cursor's MCP entries, the .test helper (Windows asks for permission once) and the "Start at login" entry move along, and Hearth's app is uninstalled; Home shows what is left if a step needs another try
  • The command line tool is now stoke (the herd, php, composer and laravel commands stay as they were)

Hearth v1.0.4

Choose a tag to compare

@github-actions github-actions released this 05 Nov 16:51
5acfbe2
  • The Windows installer and the app are now digitally signed (publisher Wolfgang Linz), so Windows no longer warns about an unknown publisher

Hearth v1.0.3

Choose a tag to compare

@github-actions github-actions released this 05 Nov 14:04
c1a1768
  • Moving over from Herd also takes C:\Program Files\nodejs\ out of the machine PATH when it is written with a trailing backslash, so node comes from Hearth afterwards
  • The check after the move shows which Node really runs: the first one on the machine PATH, then the user PATH, as Windows looks it up

Hearth v1.0.2

Choose a tag to compare

@github-actions github-actions released this 05 Nov 12:39
ef27098
  • Moving over from Herd sets up Hearth's helper service when it is missing (Windows asks for permission), instead of stopping with "The .test helper is not installed"
  • A second "Continue the move" no longer stops at "Port 80 is still in use by another program" when that program is Hearth's own web server: ports are now read correctly on Windows in any language
  • Update errors say what happened: no published release yet, or no connection to GitHub

Hearth v1.0.1

Choose a tag to compare

@github-actions github-actions released this 05 Nov 11:01
d5b7f88
  • Moving over from Herd works: "Move over" and "Undo" now really start, instead of waiting at "Starting" forever