say a note. bloop.
it's on the web.

this page did not start in an editor. it started as one rambling note. here is the route that note took to get here.

the actual note, untouched

"Can you create a demo page? I just wanna be able to showcase how I'm set up with Tailscale and Orca my local Mac and Hall and cloud flyer pages and how I can basically like make a note and then bloop and just kind of shows up on the web."

→ yes, "cloud flyer pages." the agent knew what that meant. the ramble is fine.

watch one travel

five stops, zero dashboards

type a note of your own and send it down the pipe.

  1. 01

    the note

    talk or type. no formatting, no ticket, no plan.

  2. 02

    Tailscale

    a private line between my devices. nothing is open to the internet.

  3. 03

    Orca, on my Mac

    an agent picks the note up in its own worktree and writes the page.

  4. 04

    Cloudflare Pages

    the agent pushes to GitHub. an action ships the folder. no build step.

  5. 05

    the web

    live at blooop.lol, for anybody with a browser.

my Mac
blooop.lol/demo
blooop
nothing here yet

this is a replay that runs in your browser. your note stays on this page and goes nowhere.

the setup

four pieces, each one boring on purpose

no CMS, no staging box, no servers. every piece does one job.

Tailscale

my Mac, reachable from my pocket

my phone and my Mac sit on the same private network, wherever I am. the Mac has no public address and no open ports. only my own devices can talk to it.

a local Mac

the whole workshop is one laptop

the code and the agent live on a Mac at home. there is no cloud dev box to rent or babysit. if the Mac is awake, the shop is open.

Orca

one note, one agent, one worktree

Orca hands each note to a coding agent in its own git worktree. the agent reads the repo, writes the change, and checks its work. three notes can run at once without stepping on each other.

GitHub + Cloudflare Pages

a folder of HTML, served everywhere

this site is plain files. a push to GitHub starts an action, and Cloudflare Pages serves the folder from the edge. a deploy takes about a minute and costs nothing.

the last hop

the last hop is a git push

this is the heart of the real workflow in the repo. the agent pushes, GitHub does the rest. main goes live, every other branch gets a preview link.

.github/workflows/deploy.yml
# main goes to blooop.lol. branches get previews.
on:
  push:

steps:
  - uses: actions/checkout@v4
  - uses: cloudflare/wrangler-action@v3
    with:
      command: pages deploy . --project-name=blooop-lol

the first stop is the only one you do

blooop is the free Mac app that turns the talking into text. the rest is plumbing.

see blooop