Skip to content

docs: remove stale CGO onboarding requirement #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shreyanshjain7174 merged 2 commits into from
Aug 29, 2026
Merged

docs: remove stale CGO onboarding requirement #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2dd181d
docs: remove stale CGO onboarding requirement
shreyanshjain7174 Aug 29, 2026
ed4e624
fix: make standard onboarding targets pure Go
shreyanshjain7174 Aug 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,13 @@ and welcomes outside pull requests.
## Prerequisites

- **Go 1.25.0** or later.
- **CGO enabled** (`CGO_ENABLED=1`, the default on most systems) — the
SQLite driver (`mattn/go-sqlite3`) requires a C compiler (`gcc` or
`clang`) to be on your `PATH`.
- **Docker** (optional) — only needed to run the full quickstart described
in `README.md`; not required to build, test, or contribute code.

No database, API keys, or secrets are needed to build or run the test
suite. Every test either uses an in-memory/temp-file SQLite database or a
local `httptest` server.
No C compiler, database, API keys, or secrets are needed to build or run
`make test`. The SQLite driver is pure Go. Every test either uses an
in-memory/temp-file SQLite database or a local `httptest` server. The
optional `-race` check below does require a C compiler.
Comment on lines +12 to +15

## Build, test, and lint

Expand Down
8 changes: 4 additions & 4 deletions Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
.PHONY: build build-verify run test docker lint clean

build:
CGO_ENABLED=1 go build -o bin/agentgate ./cmd/agentgw
CGO_ENABLED=0 go build -o bin/agentgate ./cmd/agentgw

build-verify:
CGO_ENABLED=1 go build -o bin/agentgate-verify ./cmd/agentgate-verify
CGO_ENABLED=0 go build -o bin/agentgate-verify ./cmd/agentgate-verify
Comment on lines 3 to +7

run:
go run ./cmd/agentgw
CGO_ENABLED=0 go run ./cmd/agentgw

test:
go test -v -count=1 ./...
CGO_ENABLED=0 go test -v -count=1 ./...

docker:
docker-compose up --build
Expand Down
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,12 @@ curl -s -X POST http://localhost:8080/admin/link \
# open the returned authorize_url, click Authorize, then re-run the /v1/act call above
```

**Inspect the receipt ledger.** Open
[`http://localhost:8080/dashboard/`](http://localhost:8080/dashboard/) and
enter the gateway URL, then the value of `AGENTGATE_ADMIN_SECRET`. The
dashboard checks the visible receipt chain locally. Use the standalone
verifier below for full cryptographic proof.

### Auditing, standalone

Verification never depends on the gateway, Docker, or a Go toolchain — it
Expand Down
Loading