Skip to content
Projects

brunnojob/devrescue has 112 GitHub stars and 0 forks. GitHot measured +49 stars in 24 hours. Last checked 2026-11-15 16:57 UTC. Last push 2026-11-12.

How these counts are measured

112 stars0 Forks +49 in 24h

Measured star growth

in 24h
+49
in 7 days
Update delayed
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Developer friction, diagnosed. Local-first CI log triage, environment checks, reviewed fixes and incident comparison. CLI + GitHub Action + workbench.

Developer Tools

README.md

Original
DevRescue

DevRescue

Less log noise. Clear evidence. Reviewed fixes.

CI Pages MIT Sponsor

Open workbench · Português · Azure setup · Sponsor

DevRescue isolates recognizable failures from build, runtime and CI logs, shows the evidence and available file/line, and suggests a concrete next step. It is deterministic, open source, and does not execute suggested commands. It cannot diagnose every failure or guarantee a fix in ten seconds.

What is included

  • Log analysis: grouped signatures, redacted evidence, available source locations, likely causes and commands to review.
  • Diagnosis: source excerpts supplied by the user, stack-specific hints and a step-by-step repair plan.
  • Compare, checklist and history: compare two logs, track manual checks, keep opt-in browser history, export Markdown/JSON.
  • Eight themes: Graphite, Dim, Midnight, Forest, Light, Mint, Rose and Sandstone, plus English/Portuguese.
  • Own account API: email/password accounts, per-user sessions, CSRF, direct GitHub OAuth with PKCE and GitHub Sponsors verification.
  • Azure sync: explicitly upload a reviewed derived report to the existing PostgreSQL database; raw/full logs stay local.
  • CLI and GitHub Action: no runtime dependencies for local troubleshooting; the root CLI also checks repository setup and offers a narrowly scoped, reviewed .env ignore fix.

Native GitHub + Azure architecture

Component Runs on Source
React/Vite interface GitHub Pages apps/web/src
Account, OAuth, sponsorship and report API Azure App Service, Node.js 22 apps/web/api
Existing users, sessions and reports Azure PostgreSQL with verified TLS apps/web/db
Tests and deployment GitHub Actions Workflows
Funding GitHub Sponsors brunnojob

The Pages application loads directly, with no iframe or external app-building runtime. Hash routes preserve navigation on Pages; old /tool.html links redirect to the native app.

Deployment status: the frontend workflow is ready for Pages. The independent Azure API needs the existing runtime's settings, direct GitHub OAuth credentials and OIDC deployment authorization described in docs/AZURE.md. A green build does not verify the real database. If the public API URL is not configured, account access displays a setup message. The existing Azure database and schemas are preserved; no remote migration is performed by this change.

GitHub Pro and Developer Program benefits can support the workflow, but Pages serves static files only; it does not host Node or PostgreSQL. No paid Azure resource is automatically created by this repository.

Local development

git clone https://github.com/brunnojob/devrescue.git
cd devrescue/apps/web
npm ci
npm run dev

Use /devrescue/ locally. For account features set the public VITE_API_BASE_URL in a private .env.local; set server secrets in the API process environment as described in the Azure guide. Build and run the independent API with npm run api:build && npm run api:start. Keep an existing database encryption key unchanged during migration.

Dependency-free CLI

From the repository root, with Node.js 22+:

node bin/devrescue.js analyze examples/build.log --markdown
node bin/devrescue.js analyze examples/build.log --json
node bin/devrescue.js doctor .

The root CLI and Action use the repository troubleshooting engine. The web app includes its newer browser analyzer and a separately tested compiled CLI companion under apps/web/bin. Both are signature-based; findings may differ. Neither uploads logs or runs suggestions.

GitHub Action

- uses: actions/checkout@v4
- name: Analyze an existing log
  if: always()
  uses: brunnojob/devrescue@main # Pin a reviewed commit SHA in production.
  with:
    log-path: ./ci.log
    fail-on-findings: 'false'

Create ci.log in an earlier step. The action does not download job logs automatically. It writes sanitized Markdown to the job summary and supports Linux, Windows and macOS, including the older Bash shipped on macOS.

Validation

# Root CLI and Action package
npm test
npm run demo
npm pack --dry-run
# Web, database behavior and API boundary
cd apps/web
npm ci
npm test
npm run lint
npm run build
npm run typecheck
npm run api:build

Database isolation and trial behavior are tested with PGlite, without touching production. Real Azure connectivity must be checked separately using the deployment guide.

Privacy and support

Redaction is pattern-based. Review every report before sharing or uploading it. Account features make explicit API calls; browser analysis itself does not send logs to a model or analytics service. See limitations and security.

Support maintenance through GitHub Sponsors. Hosted access retains the three-hour trial tied to a verified GitHub identity and sponsor access for monthly or confirmed one-time support. Server-side access checks protect report operations. The source and local CLI remain MIT licensed.