amber new
Run from: any directory; NAME controls where the project is created.
amber new NAME [options]
Options
| Option | Default | Meaning |
|---|---|---|
| `--type web | native` | web |
-d, `--database pg |
mysql | sqlite` |
-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.
amber new my_app
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
The first two commands generate the same web application. Omitting --type
is the recommended first run; the explicit form is useful in automation.
Web template contract
The generated web app contains:
amberframework/amberpinned to2.0.0-beta.5- Grant pinned to the reviewed V2 commit
- SQLite by default, or the selected PostgreSQL/MySQL driver
config/database.crand typed per-environment database URLs- Micrate-powered database commands in the compiled CLI
- Crystal
>= 1.20.0, < 2.0 - ECR layout and homepage
- authored CSS, JavaScript, images, fonts, and files under
app/assets/ - fingerprinted output and a strict manifest under ignored
public/assets/ - manifest-aware ECR helpers and
amber assets build|check - typed development, test, and production YAML
- web, API, and static pipelines plus routes
- homepage request spec and
bin/build directory - no attachment shard, personal Amber fork, moving framework branch, or unselected database driver
The database option installs a complete persistence choice. SQLite is the zero-server first run; PostgreSQL and MySQL require their matching server.
The generator builds the initial manifest before it finishes, including with
--no-deps. Authored files belong in source control; generated
public/assets/ output does not. See the web template
guide for the exact file map and ownership boundary.
After generation
Run from: the generated application root after cd my_app.
cd my_app
# Needed only when --no-deps was used:
shards install
amber assets check
crystal spec
crystal build src/my_app.cr -o bin/my_app
amber generate scaffold Pet name:string:required species:string:required adopted:bool
amber database migrate
amber watch
Verify /, then follow the fingerprinted CSS, JavaScript, image, and font URLs
rendered into the HTML and compiled CSS. Those URLs come from
public/assets/manifest.json; a request to an old raw /css or /js path is
not an asset-manifest verification.
--type native remains available for contributors and early adopters, but it
is not part of the Amber V2 beta install/build guarantee. Read the native
preview guide before evaluating it.