cron
- invoke process on scheduledeploy
- invoke process when Lair is deployed; used to start long-running processes such as active serviceshttp
- invoke process when a request is made to a HTTP endpointdeploy
and http
triggers generate custom endpoints for your Lair. See Endpoints for more details on how to manage endpoints. cron
triggers only invoke processes in your Lair's production environment. See Deployments for more details on how to deploy your tool to your Lair's production environment..triggers
file stored within your Lair’s root directory. Open the .triggers
file from your file system and select “+ New Trigger” to add a new trigger..triggers
file. You will also have to “Push” your workspace’s file system to update this configuration on your remote Lair..triggers
file, select an existing trigger to open the configuration modal. Press “Run” to execute your trigger’s run command and start the process execution. See Processes for more details on how to view and manage processes.http
trigger routes HTTP requests to independent, asynchronous processes running in separate containers, while using the deploy
trigger routes HTTP requests to a running service process in a single container. http
triggers vs. running service processes deployed via the deploy
trigger will ALWAYS have higher latency due to serverless execution. When a request is made to an http
trigger, the WayScript system must provision a new container, install any new dependencies, and attach logs before the request can be returned. http
triggers to your Lair and specify different paths for each trigger, but setting up a running service process gives you unlimited scalability of endpoints and more fine-tuned control of endpoint characteristics. http
triggers will be torn down on process exit, and therefore in cases of low volume of requests, this approach will use less system runtime.