# `amber new`

```bash
amber new NAME [options]
```

## Options

| Option | Default | Meaning |
|---|---|---|
| `--type web|native` | `web` | Web is supported; native is preview |
| `-d`, `--database pg|mysql|sqlite` | `pg` | Records metadata and suggested URLs |
| `-t`, `--template ecr` | `ecr` | Amber V2 supports ECR only |
| `--no-deps` | off | Skip automatic `shards install` |
| `-y`, `--assume-yes` | off | Disable interactive prompts |

`NAME` may be a simple name, relative path, absolute path, or `.`. For a path,
the final component becomes the project name. Paths containing spaces are
rejected.

```bash
amber new my_app --type web
amber new projects/admin --type web -d sqlite
amber new /tmp/amber_smoke --type web --no-deps
amber new . --type web
```

## Web template contract

The generated web app contains:

- `amberframework/amber` pinned to `2.0.0-beta.2`
- Crystal `>= 1.20.0, < 2.0`
- ECR layout and homepage
- typed development, test, and production YAML
- web, API, and static pipelines plus routes
- homepage request spec and `bin/` build directory
- no ORM, database driver, attachment shard, or personal fork

The database option does not install persistence. It preserves intent for later
tooling while keeping the first build independent of a database.

## After generation

```bash
cd my_app
# Needed only when --no-deps was used:
shards install
crystal spec
crystal build src/my_app.cr -o bin/my_app
amber watch
```

Verify both `/` and `/css/app.css`.

`--type native` remains available for contributors and early adopters, but it
is not part of the Amber V2 beta install/build guarantee.