Skip to content

Fix Neon seed docs #4

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
hudsonaikins merged 1 commit into from
Jul 2, 2026
Merged

Fix Neon seed docs #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 5 additions & 5 deletions docs-site/content/docs/cloudflare-neon-deployment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,12 @@ export DATABASE_URL="postgresql://USER:PASSWORD@HOST/DB?sslmode=require"
uv run --extra db agent-permit db migrate
```

Seed public fixture scans:
Seed the database by running deterministic fixture scans. The public demo export is curated for docs and does not include every file required by `agent-permit ingest`.

```bash
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/risky-ci-agent
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/risky-mcp-agent
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/safe-agent
uv run --extra db agent-permit scan tests/fixtures/safe-agent --ci --run-id neon-seed-safe-agent
uv run --extra db agent-permit scan tests/fixtures/risky-ci-agent --ci --run-id neon-seed-risky-ci-agent || true
uv run --extra db agent-permit scan tests/fixtures/risky-mcp-agent --ci --run-id neon-seed-risky-mcp-agent || true
```

Check the Worker:
Expand Down Expand Up @@ -114,7 +114,7 @@ Requires explicit infrastructure approval.
2. Copy the Postgres connection string.
3. Store it locally in `.env`.
4. Run `agent-permit db migrate`.
5. Ingest public fixture scans.
5. Run the three fixture seed scans.
6. Query `/api/snapshot` locally through Wrangler.

### 3. Deploy Worker API
Expand Down
10 changes: 5 additions & 5 deletions docs/cloudflare-neon-deployment-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,12 +54,12 @@ export DATABASE_URL="postgresql://USER:PASSWORD@HOST/DB?sslmode=require"
uv run --extra db agent-permit db migrate
```

Then seed data from local proof artifacts:
Then seed data by running deterministic fixture scans. The public demo export is intentionally curated for docs and does not contain every file needed by `agent-permit ingest`.

```bash
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/risky-ci-agent
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/risky-mcp-agent
uv run --extra db agent-permit ingest docs/demo-artifacts/public-fixture-scans/safe-agent
uv run --extra db agent-permit scan tests/fixtures/safe-agent --ci --run-id neon-seed-safe-agent
uv run --extra db agent-permit scan tests/fixtures/risky-ci-agent --ci --run-id neon-seed-risky-ci-agent || true
uv run --extra db agent-permit scan tests/fixtures/risky-mcp-agent --ci --run-id neon-seed-risky-mcp-agent || true
```

### Do not use D1 first
Expand Down Expand Up @@ -213,7 +213,7 @@ Steps:
2. Copy pooled or direct Postgres connection string.
3. Store it locally in `.env`.
4. Run `agent-permit db migrate`.
5. Ingest public fixture scans.
5. Run the three fixture seed scans.
6. Query `/api/snapshot` locally through Wrangler.

### 3. Deploy Worker API
Expand Down
Loading