Developer Guides

Use robots.txt for crawl guidance, not security. The safest workflow is to keep public pages and assets crawlable, block low-value paths, and verify the file from the domain root.

Redirect changes are small but risky. A safe workflow generates a narrow rule, validates Nginx syntax, tests Location headers and keeps rollback simple.

Most API request bugs are easier to fix before the request is sent. Start with valid JSON, then check model-family parameters and only then debug application code.

Local stacks are easier to maintain when docker-compose.yml describes services and .env.example documents configuration without real secrets.

A 429 response means the request was understood but rate limited. The fastest fix is to inspect headers, reduce concurrency and prove the behavior with a minimal request.

JWT time bugs often come from seconds versus milliseconds, timezone confusion or trusting decoded payloads without signature verification.

Class not found errors usually come from autoload configuration, namespace mismatches, missing packages or case-sensitive file paths after deployment.

Undefined property errors are usually data-shape, timing or wrong-object bugs. The first useful clue is the stack frame pointing into your own code.

A useful sitemap contains canonical, crawlable URLs that return 200 responses. It should not be a dump of every route your application can produce.

cURL is the simplest way to separate API behavior from SDK, framework or frontend code. Build a minimal request first, then compare it with the failing implementation.