{"title":"Routing","description":"Connect Amber V2 pipelines, paths, and controller actions","section":"guides","version":"v2","path":"guides/routing","canonical_url":"https://amberframework.org/docs/v2/guides/routing","markdown_url":"https://amberframework.org/docs/v2/guides/routing.md","inherited":false,"content_markdown":"# Routing\n\nAmber compiles the routes in `config/routes.cr`. Each route selects a pipeline,\nmatches an HTTP method and path, then dispatches to a controller action.\n\nThe generated V2 web application starts with separate `web` and `static`\npipelines. Keep that separation: request/session behavior belongs to the web\npipeline, while files under `public/` are served through the static pipeline.\n\n- [Pipelines](pipelines.md) — compose request handlers in execution order.\n- [Routes](routes.md) — map paths, resources, namespaces, and constraints.\n\nRun `amber routes` from the project root to inspect the routes declared in\n`config/routes.cr`. The compiler and request specs remain the source of truth\nfor whether those routes dispatch successfully."}