{"title":"Amber 2.0 Beta","description":"Install, verify, and evaluate Amber 2.0.0-beta.5","section":"","version":"v2","path":"","canonical_url":"https://amberframework.org/docs/v2","markdown_url":"https://amberframework.org/docs/v2.md","inherited":false,"content_markdown":"# Amber 2.0 Beta\n\nAmber `2.0.0-beta.5` is available for evaluation. The V2 release train remains\na prerelease, but the web path is deliberately backwards compatible and mostly\nadditive. Pin the exact beta, test upgrades, and do not treat it as a formal\nproduction-support promise.\n\nThe release-gated first-run path is a server-rendered ECR web application\ncreated by the standalone Amber CLI. It includes routing, controllers, typed\nconfiguration, sessions, Grant ORM, Micrate migrations, SQLite, fingerprinted\nstatic assets, tests, and a development watcher without requiring a database\nserver.\n\n**Run from: a parent directory where `my_app/` can be created. Commands after\n`cd my_app` run from the generated application root.**\n\n```bash\nbrew install amberframework/amber_cli/amber_cli\namber new my_app\ncd my_app\namber generate scaffold Pet name:string:required species:string:required adopted:bool\namber database migrate\ncrystal spec\namber watch\n```\n\nWeb is the default application type. `amber new my_app --type web` is the\nexplicit equivalent. Native generation is a separate preview surface.\n\nStart with [Installation](getting-started/installation/) for the platform\nmatrix, checksums, and troubleshooting, then follow the\n[web-app walkthrough](getting-started/). The\n[web template reference](guides/web-template/) explains every generated layer\nand its release boundary.\n\n## What is in the framework beta\n\n- MVC controllers and ECR views\n- routing, pipelines, constraints, and named routes\n- typed request schemas and validation\n- memory-backed jobs, sessions, and WebSocket pub/sub\n- mailer APIs\n- typed YAML configuration with environment-variable overrides\n- Grant ORM with SQLite by default and PostgreSQL/MySQL options\n- Micrate-powered migrations and database maintenance commands\n- database-backed model and HTML CRUD scaffold generators\n- deterministic CSS, JavaScript, image, font, and file fingerprinting\n- manifest-aware ECR helpers, SRI, compression, and immutable asset caching\n- standalone CLI and diagnostics LSP\n\n## What is preview\n\nGenerated authentication and API resources, Gemma file attachments, and\nnative-app generation have useful code and documentation, but they are not part\nof the beta web-app release gate. Preview pages are labeled so new users do not\nmistake them for the supported path.\n\nSee [Beta support](beta-support/) for the exact platform and generator matrix.\n\n## Migrating\n\nAmber V2 removes Kilt and Slang, adopts typed configuration, and extracts the\nCLI from the framework repository. The new CLI template selects its driver and\nGrant explicitly; the framework shard itself remains independent of an ORM.\nExisting apps should follow the [migration guide](migration-guide/) and pin the\nbeta instead of a moving development branch.\n\n## Help\n\n- [Discord](https://discord.gg/vwvP5zakSn)\n- [Framework issues](https://github.com/amberframework/amber/issues)\n- [CLI issues](https://github.com/amberframework/amber_cli/issues)\n- [Homebrew issues](https://github.com/amberframework/homebrew-amber_cli/issues)"}