rays/ipx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

CLAUDE.md and prod-check: ipx-web is what serves port 8099 now (#203)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ray Slakinski
2026-10-12 14:21:53 +00:00
parent 0c820bbde1
commit 3bab6210c5
2 changed files with 26 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
.claude/skills/ipx-prod-check/SKILL.md
View File

@@ -1,6 +1,6 @@
---
name: ipx-prod-check
description: Look for problems in production ipx (the iPX and ipx-directory containers on Tower) from its logs in Loki, its traces in Tempo and its metrics in Prometheus, and file what is found as Gitea issues. Use when asked to check on production, look for issues or errors in ipx, see why something is slow or failing in production, review the logs, or investigate a report about the live site.
description: Look for problems in production ipx (the iPX, ipx-web and ipx-directory containers on Tower) from its logs in Loki, its traces in Tempo and its metrics in Prometheus, and file what is found as Gitea issues. Use when asked to check on production, look for issues or errors in ipx, see why something is slow or failing in production, review the logs, or investigate a report about the live site.
---
# Checking production ipx
@@ -225,6 +225,17 @@ it. A snapshot whose `refused_private` is not 0 means an ipx server tried to sen
private: find which in that server's log, since the directory refuses it but the sender should not
have sent it. Many `feed check failed` lines for one feed are the publisher's, not the directory's.
## The page
`ipx-web` (Caddy) serves the page and passes the API to ipx (#203). It logs only its own start and
errors, not requests: ipx's access log still has every API call, and a page that fails to load
shows there as `/api/page-check` answering something other than 204, 303 or 302.
```sh
docker ps --filter name=ipx-web --format '{{.Status}}'
docker logs --since 24h ipx-web 2>&1 | grep -v '"level":"info"' | tail
```
`docker logs` and `docker exec iPX ipx ...` are fine. Do not query production's Postgres
directly: ask the user if a question needs the database.