skygear.yaml
. Configurations can be divided into two types, microservice and web hooks respectively.deployments
, while those of hooks are under the key hooks
.api_version
declares the API version. Use the value v2.1
for now.deployments
contains a list of deployment items. In the above sample, there are two micro-service deployment items, named backend
and frontend
.deployments
).port
key specifies the TCP port the micro-service is listening for. Required.command
key specifies the command of a microservice. It will be translated to the args
key of Kubernetes deployment.template
, context
, and image
keys specify a microservice item's Docker image source. For details, refer to Deployment Image documentation.environment
key specifies the environment variables of a microservice item.name
and value
.secret
key. name
is optional, with use the Secret's name when not given.index.html
hooks
key. Each entry represents a web-hook handler.event
key reflects the event name that the web-hook handler would handle. The same event name can appears multiple times in the list. For list of event names, refer to Web-hooks documentation.path
key specifies the location of web-hook handler. It can be an absolute URL (e.g. https://example.com
), or path (which would be resolved to absolute URL based on the app endpoint).