composer require --dev spryker-sdk/spryk
This is a development only "require-dev" module. Please make sure you include it as such.
Spryks are some sort of code generators for Spryker. Writing code is often a very repetitive task and you often need to write a lot code just to follow Spryker's clean and complex architecture. To take a way the monkey work from writing wir up code and move faster towards writing business code Spryks are born.
Spryks are written with the help of yml files. The filename of the yml file represents also the Spryk name. In most cases the Spryk yml contains arguments which are needed to fullfill the Spryk build run. Almost all Spryks need the module name to run properly. Some Spryks require much more arguments.
The vast majority of the Spryks need to execute other Spryks before the called Spryk can run. For example Add a Zed Business Facade needs to have a properly created module before the Facade itself can be created. Therefore Spryks have pre and post Spryks and with the call of one Spryk many things can and will be created for you.
vendor/bin/spryk-run- Runs Spryks in your projectvendor/bin/spryk-dump- Lists all available Spryksvendor/bin/spryk-build- Builds a cache file for all Spryk arguments
Examples:
- To get a list of top level spryks run
vendor/bin/spryk-dump. - To get a list of all available spryks run
vendor/bin/spryk-dump --level=all. - To get a list of all options available for a specific spryk run
vendor/bin/spryk-dump {SPRYK NAME}. - To execute one Spryk run
vendor/bin/spryk-run {SPRYK NAME}. - To reflect changes in Spryk arguments and generate a new cache for them run
vendor/bin/spryk-build.
When you run a Spryk, the console will ask you for all needed arguments to build the Spryk. You also have the ability to pass all known arguments on the console by using --{argument name}={argument value}.