<One paragraph. What they'll build, not what topics get covered. Name the thing they walk away with.>
- — <what it does for them, not what it is>
- — <…>
- — <…>
- — <…>
Budget minutes, and do this the day before, not five minutes before. <Say what happens if they don't — e.g. "this session starts at step 4 and you won't be able to follow along.">
Sign up at .
Click the badge above. First boot takes a few minutes — it installs the Tiger CLI. You'll see a banner in the terminal when it's done.
tiger auth login --headless--headless prints a short code and a URL. Open the URL in any browser on any machine,
enter the code, pick your project. This is the flow designed for a terminal that can't
open your browser, which is exactly a Codespace.
tiger service listtiger service create --name <workshop>-workshop --cpu 500 --memory 2<Say why this size. Free — --cpu shared --memory shared — is enough unless the workshop
needs real storage or compute.>
Creating a service also makes it your default, so nothing below needs a service ID.
tiger db query -c "SELECT version()"<End with one command whose output proves they're set, and say bluntly what to do if it doesn't work.>
minutes. Each section is self-contained, so falling behind on one doesn't lock you out of the next.
| File | What it does |
|---|---|
sql/1-<name>.sql |
<…> |
sql/2-<name>.sql |
<…> |
Run a whole file:
tiger db query -f sql/1-<name>.sqlOr one section at a time, so you can read the output as you go:
tiger db query -c "SELECT ..."- Workshop day: ask in the chat.
- Anytime: Tiger Data docs or Community Slack.
<Every failure you actually hit while building this. This section earns its length — it is the difference between an attendee unblocking themselves and an attendee going quiet.>
<Symptom, in the words they'd use>
Don't leave services running you aren't using:
tiger service list
tiger service delete <service-id> --confirmMIT — see LICENSE.