agentleFS
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/claude/gapi-setup/CLAUDE.md

Seeed-Jetson-DevelopTool / gapi-setup

CLAUDE.md57 starsChanged 4 months agoMITView on GitHub

Deploy Gapi embeddable API gateway on Jetson Orin for streaming AI micro service integrations. Covers Docker-based installation, workflow engine setup, and community micro services. Requires any Jetson Orin with Docker and 1.3GB storage.

  • Pipes a download into a shell

The file

We split this CLAUDE.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run one phase at a time. After each phase:

    line 12
  2. Very specific:

    If output contains [STOP] → stop immediately, consult the failure decision tree below.

    line 14
  3. Very specific:

    If output ends with [OK] → tell the user "Phase N complete" and proceed to the next phase.

    line 15
  4. Distinctive:

    Verify the container is running:

    line 39
  5. Distinctive:

    Follow the instructions in the blue box to download your custom configuration

    line 73
  6. Distinctive:

    Follow the per-service install instructions below that

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Getting Started with Gapi on Jetson


Execution model

Run one phase at a time. After each phase:

  • Relay all command output to the user.
  • If output contains [STOP] → stop immediately, consult the failure decision tree below.
  • If output ends with [OK] → tell the user "Phase N complete" and proceed to the next phase.

Prerequisites

RequirementDetails
HardwareAny NVIDIA Jetson Orin
SoftwareDocker installed and running
Storage≥1.3 GB for Gapi server
NetworkRequired for Docker pull and web access

Phase 1 — Install Gapi server (~5 min)

mkdir ~/gapiData && cd ~/gapiData
curl -L https://raw.githubusercontent.com/genai-nerds/Gapi/main/gapiConfigs.zip -o gapiConfigs.zip
unzip -q gapiConfigs.zip
docker run -d --name gapi --network host -v ~/gapiData:/opt/gapi/vdata genainerds/gapi:arm64 /bin/bash -c "cd /opt/gapi/bin && ./startGapi.sh"

Verify the container is running:

docker ps | grep gapi

[OK] when the gapi container is listed as running. [STOP] if Docker pull or container start fails.


Phase 2 — Log in to Gapi WebUI (~1 min)

Open a browser and navigate to:

http://<jetson-ip>:8090

Default credentials:

  • User: root
  • Password: !gapi2024

Change the password in Settings after first login. SSL cert setup is covered in the Gapi docs.

[OK] when you can log in and see the Gapi dashboard.


Phase 3 — Explore workflows and micro services

Workflows visually connect Nodes that talk to Micro Services and APIs. Each Node can append or reference rolling Transaction data.

To set up Community Micro Services:

  1. Go to the Micro Services tab in the Gapi UI
  2. Follow the instructions in the blue box to download your custom configuration
  3. Follow the per-service install instructions below that

Community Micro Service storage requirements: ~4 GB to ~10 GB each.

[OK] when at least one micro service is connected and visible in the UI.

For workflow tips, micro service architecture details, and custom on_message handlers, see references/source.body.md.


Failure decision tree

SymptomAction
docker: command not foundInstall Docker: curl https://get.docker.com | sh && sudo systemctl enable --now docker
Docker pull failsCheck internet connectivity. Verify Docker daemon is running with sudo systemctl status docker.
Container exits immediatelyCheck logs: docker logs gapi. Ensure ~/gapiData contains the unzipped config files.
Cannot access port 8090Verify container is running with docker ps. Check firewall. Try http://localhost:8090 from the Jetson itself.
Login failsUse default credentials root / !gapi2024. Clear browser cache if needed.
Micro service won't connectEnsure the micro service container has network access. Check the streaming websocket connection in logs.

Reference files

  • references/source.body.md — full original Seeed tutorial with workflow diagrams, micro service architecture, and integration details (reference only)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.