Download the PHP package spryker-sdk/spryk without Composer
On this page you can find all versions of the php package spryker-sdk/spryk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package spryk
Spryk Module
Installation
This is a development only "require-dev" module. Please make sure you include it as such.
What are Spryks?
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.
How to use Spryks?
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}.
Extending Spryk
Adding Spryks
You can add your own Spryks by creating a Spryk definition in your projects config/spryk/spryks/ directory.
Spryk definitions in this directory will be found by the tool and can be executed as usually.
Adding Spryk templates
You can add your own Spryk templates by creating a template in your projects config/spryk/templates/ directory.
Spryk templates in this directory will be found by the tool and can be used in your Spryks.
Configuration
Spryks need some project related configurations. These are passed automatically to the tool.
The following configurations will be passed to the Spryk tool:
Spryker\Shared\Kernel\KernelConstants::PROJECT_NAMESPACESpryker\Shared\Kernel\KernelConstants::PROJECT_NAMESPACESSpryker\Shared\Kernel\KernelConstants::CORE_NAMESPACES
