All deployment configuration of an app is defined with
skygear.yaml. Configurations can be divided into two types, microservice and web hooks respectively.
A sample deployment configuration file looks like this:
app: my-appapi_version: v2.1deployments:- name: backendtype: http-servicepath: /apiport: 8080context: backendtemplate: nodejs:12environment:- name: SERVER_PORTvalue: "8080"- secret: DATABASE_URL- name: frontendtype: http-servicepath: /port: 8080context: frontendtemplate: nodejs:12hooks:- path: /api/after_user_createevent: after_user_create
Configurations of the microservices are declared under the key
deployments, while those of hooks are under the key
The top-level key
api_version declares the API version. Use the value
v2.1 for now.
The top-level key
deployments contains a list of deployment items. In the above sample, there are two micro-service deployment items, named
The name of a deployment item, must be unique in this list (i.e. under the key
Indicates the path which the deployment item would be mounted and be available at. For details, refer to Routing documentation.
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.
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.
For environment variables, it can be configured with a literal pair of
For environment variables using a Kubernetes Secret as the source, use the
name is optional, with use the Secret's name when not given.
The relative path to static assets.
The file to serve when the path cannot be found. The HTTP status code of response is 200.
The file to serve when the path cannot be found. The HTTP status code of response is 404.
The name of index file. Default to
The cache expiry time in seconds. Valid value ranged from 0 to 604800 (7 days).
Web-hook configurations are put under the
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).