Amber generators can use a recipe to generate your application, and scaffold your application with controllers, models and views. Using a recipe you can get started with an amber application that extends or modifies the standard built in generator or provides additional features. For example you might want an API application that only renders JSON or use React or AngularJS for views.
Recipes are provided by independent contributors in their own GitHub accounts. To use a recipe you specify the GitHub account name and recipe name in the format githubaccount/recipe_name. Recipe creators should add the amber-recipe topic to the GitHub repository for the recipe.
See the Amber Recipes that are available on GitHub for a list of recipes that have been created by recipe contributors. Visit the recipe repository for more information about each recipe.
Add a recipe name command line argument to create a new amber application from the recipe. The recipe name that you use to generate the application is saved so that when you generate controllers, models and views with the scaffold generator the same recipe is used - you don't have to specify the recipe each time.
amber new [OPTIONS] NAMEGenerates a new Amber projectArguments:NAME name/path of projectOptions:-d Select the database database engine, can be one of: pg | mysql | sqlite(default: pg)--deps Installs project dependencies, this is the equivalent of running (shards update)-m Select the model type, can be one of: granite | crecto(default: granite)--no-color Disable colored output-r Use a named recipe. See documentation at https://docs.amberframework.org/amber/cli/recipes.-t Selects the template engine language, can be one of: slang | ecr(default: slang)-h, --help show this help
amber new microsecond-blog -r damianham/amber_modular will generate a skeleton Amber application in
./microsecond-blog using the amber_modular recipe that was provided by the GitHub user damianham.
You can have a running web application in a matter of minutes:
amber new microsecond-blog -r damianham/amber_modular --deps
Now open a web browser for your new amber app at http://localhost:3000.
Full example in terminal:
$ amber new microsecond-blog -r damianham/amber_modularRendering App microsecond-blog in ./microsecond-blognew .amber.ymlnew .amber_secret_keynew .gitignorenew .travis.ymlnew config/application.crnew config/database.yml... [clipped]new src/views/layouts/_nav.slangnew src/views/layouts/application.slangnew src/microsecond-blog.cr$ cd microsecond-blog/$ shards installUpdating https://github.com/amberframework/amber.gitUpdating https://github.com/luislavena/radix.git... [clipped]Installing garnet_spec (0.1.1)Installing selenium (0.3.0)$ amber watch02:58:23 Watcher | (INFO) Watching 22 files (server reload)...02:58:23 Watcher | (INFO) Building project App01...02:58:31 Watcher | (INFO) Terminating app App01...02:58:31 Watcher | (INFO) Starting App01...02:58:31 NodeJS | (INFO) Installing dependencies...02:58:31 NodeJS | (INFO) Watching public directory02:58:31 Server | (INFO) Amber 0.10.0 serving application "App01" at http://0.0.0.0:300002:58:31 Server | (INFO) Server started in development.02:58:31 Server | (INFO) Startup Time 00:00:00.00018200002:58:31 Watcher | Watching 10 client files...
The generators in amber are a great way to get an application up and running quickly. In addition, they help keep code consistent and following convention. See the Generate option of the Command Line Tool for details about the generate command.
Once an application is generated with a recipe, it will be used by future generate or scaffold commands to maintain consistency with the recipe. For example, an application generated with a "json-api" recipe will continue to generate controllers and views according to the "json-api" recipe.
When a recipe doesn't quite suite your requirements, it's easy to modify. Recipes are application stubs written in Liquid. Modified recipes can be stored and sourced locally or made available to other Amber users from your own GitHub account.
Download a recipe that you want to modify, extract it, and use the extracted recipe on the command line. For example:
git clone https://github.com/damianham/amber_modular.git ~/mymodular
# modify the recipe in ~/mymodular some way
amber new microsecond-blog -r ~/mymodular
Now open a web browser at http://localhost:3000.
It is important to give the absolute path to the recipe folder as the recipe command line argument to ensure that the recipe can be found when generating subsequent artifacts.
The best way to do this is to fork an existing recipe and then modify it. Visit the GitHub repository of a recipe you want to use as a starting point, e.g. one of the recipes listed above in the Available recipes section, and create your own fork. After you have modified the recipe and pushed your changes you can create apps with your recipe with:
amber new myapp -r your_github_name/your_recipe_name
You can easily contribute your recipe to the Amber community. By adding the amber-recipe topic to your recipe repository on GitHub, it will be added to the list of Amber Recipes.