[netanelgilad]

Summary

Adds tanstack-start/, a server-rendered guestbook built on the TanStack Start template the Base44 builder seeds, and a workflow that deploys it with the Base44 CLI on every push to main.

• App:
  • A GuestbookEntry entity: anyone can read and sign; only admins can edit or delete entries.
  • Two server functions in src/lib/server-fns.js, one to list entries and one to sign (input checked with zod). Both run as the visitor, so the entity's access rules apply.
  • A home page that renders the list on the server and has a form to sign.
• Workflow: .github/workflows/deploy-tanstack-start.yml runs on pushes to main that touch tanstack-start/, and can also be started by hand.
  • It runs npm ci, installs base44@0.2.0, then base44 deploy -y --build --git-hash "$GITHUB_SHA".
  • --build puts the app ID into the build. --git-hash deploys by the commit; a full-stack build needs it (base44/cli#643).
  • One deploy runs at a time, and a running deploy is never cancelled.
• Docs: a README for the app (get started, deploying from GitHub, how the pieces fit) and a row in the repo index.

Setup before the first run

In Settings → Secrets and variables → Actions, add:

Name	Kind	Value
BASE44_API_KEY	Secret	A workspace API key (b44k_…)
TANSTACK_START_APP_ID	Variable	The app to deploy to

Testing

• Install and build: npm ci and npm run build succeed. They produce dist/client, dist/server and .wrangler/deploy/config.json.
• Lint: ESLint passes on the changed files.
• Config: the CLI's project parser reads base44/config.jsonc and the entity, including its access rules.
• Workflow: the YAML parses.
• Not yet tested: a real deploy. It needs the secret and variable above; once they're set, run the workflow by hand from the Actions tab.
• Local dev: base44 dev for TanStack apps depends on base44/cli#659, which hasn't merged yet.

---

Generated by Claude Code