feat: add blazecrawl doctor command - #47
Merged
danishxsethi merged 2 commits intoSep 28, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
blazecrawl doctorwith a human-readable pass/fail report for Playwright/Chromium availability, configured server/readyreachability, and configured API-key validity. API-key validation uses an authenticated crawl-status lookup that performs no egress: a valid key reaches the route and returns 404 for the synthetic job id, while an invalid key returns 401. The command exits 0 only when all required checks pass, with focused tests for reporting and exit status.Closes #17.
Local pytest/Playwright validation was not run because the connected development machine is currently offline.