What
PR #134 (commit 6fef967) updated repository references after the project rename from "Webhook Management Platform" to "hooketh", but only touched CONTRIBUTING.md/README.md. Several other files still reference the old name/path and are broken as a result:
docker/validate.sh:164 — if docker images | grep -q webhook-management-platform; then can never match. docker-compose.yml builds/tags images from the actual directory name (hooketh, e.g. hooketh-app), so this check always falls through to the warning branch: make validate (or running the script directly) will print "Application Docker images not found. Run 'make build' to build them." even immediately after a clean, successful build.DEVELOPMENT.md:39-40:
git clone https://github.com/morcen/hooketh.git
cd webhook-management-platform
hooketh, not webhook-management-platform. Any new contributor following this doc verbatim gets a No such file or directory before they run a single other command.
Other docs likely carry the same stale branding/paths and are worth a sweep in the same pass: LARAVEL-CLOUD.md, DEVELOPMENT-SETUP.md, ARCHITECTURE.md, scripts/verify-deployment.sh.
Why it matters
docker/validate.sh is the sanity-check script make validate runs to confirm the stack is healthy; it now always reports a false negative for "images built," undermining trust in the script for every future run. DEVELOPMENT.md is the first thing a new contributor opens — its opening commands not working is a bad first impression and wastes their time debugging a "cd: no such file" error that has nothing to do with their environment.
Suggested fix
docker/validate.sh:164: replace the hardcoded webhook-management-platform string with a check against the actual compose project name (e.g. docker images | grep -q "^hooketh-" or derive the project name dynamically via basename "$(pwd)" / docker compose config --images).DEVELOPMENT.md:40: change cd webhook-management-platform to cd hooketh.- Grep the whole repo for
webhook-management-platform / Webhook Management Platform outside of intentionally-historical contexts (e.g. grep -rln "webhook-management-platform" --include="*.md" --include="*.sh" .) and fix any remaining stale references in one follow-up pass.
What
PR #134 (commit
6fef967) updated repository references after the project rename from "Webhook Management Platform" to "hooketh", but only touchedCONTRIBUTING.md/README.md. Several other files still reference the old name/path and are broken as a result:docker/validate.sh:164—if docker images | grep -q webhook-management-platform; thencan never match.docker-compose.ymlbuilds/tags images from the actual directory name (hooketh, e.g.hooketh-app), so this check always falls through to the warning branch:make validate(or running the script directly) will print "Application Docker images not found. Run 'make build' to build them." even immediately after a clean, successful build.DEVELOPMENT.md:39-40:hooketh, notwebhook-management-platform. Any new contributor following this doc verbatim gets aNo such file or directorybefore they run a single other command.Other docs likely carry the same stale branding/paths and are worth a sweep in the same pass:
LARAVEL-CLOUD.md,DEVELOPMENT-SETUP.md,ARCHITECTURE.md,scripts/verify-deployment.sh.Why it matters
docker/validate.shis the sanity-check scriptmake validateruns to confirm the stack is healthy; it now always reports a false negative for "images built," undermining trust in the script for every future run.DEVELOPMENT.mdis the first thing a new contributor opens — its opening commands not working is a bad first impression and wastes their time debugging a "cd: no such file" error that has nothing to do with their environment.Suggested fix
docker/validate.sh:164: replace the hardcodedwebhook-management-platformstring with a check against the actual compose project name (e.g.docker images | grep -q "^hooketh-"or derive the project name dynamically viabasename "$(pwd)"/docker compose config --images).DEVELOPMENT.md:40: changecd webhook-management-platformtocd hooketh.webhook-management-platform/Webhook Management Platformoutside of intentionally-historical contexts (e.g.grep -rln "webhook-management-platform" --include="*.md" --include="*.sh" .) and fix any remaining stale references in one follow-up pass.