-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Thomas Gossmann edited this page Apr 13, 2016
·
9 revisions
Let's see what keeko tools can do:
Mostly used for code generation
-
keeko init
- inits a skeleton package into a keeko package -
keeko generate:action
- generates actions for a module -
keeko generate:domain
- generates a domain object -
keeko generate:serializer
- generates a serializer -
keeko generate:response
- generates responses for available actions in a module -
keeko generate:api
- generates swagger api for a module -
keeko magic
- runs all of the above in one step
They all work pretty much similarly. They either take a model option or a name argument. When neither is provided then the desired object(s) are generated for all found models.
Some examples:
# 1) Generates an action with the name "request-password":
keeko generate:action request-password
# 2) Generates a serializer for the "user" model:
keeko generate:serializer --model user
# 3) Generates domain objects for all given models:
keeko generate:domain
To manage keeko installations
- *
keeko install
- Creates a new keeko project and runscomposer install --no-dev
- *
keeko setup
- Installs database and keeko core system - *
keeko app:setup vendor/name
- Installs an app with a given url - *
keeko module:activate vendor/name
- Activates a module - *
keeko module:deactivate vendor/name
- Deactivates a module - *
keeko update
- Runscomposer update --no-dev
and updates everything - *
keeko require
- to install a new package (without triggerig dev updates)
Note: * These tasks are still todo