Emitter
Deploy triggers that run a batch program when a chosen database table changes.
Emitter runs a batch program whenever a chosen database table changes, for event-driven server logic rather than a request-response endpoint. Its Configuration step replaces Launch Settings entirely, since each trigger already names the program it runs.
Create an Emitter deployment
Open the project and click Deploy
Open the project, click Deploy, then select Emitter from the Backend group.
Emitter Configuration: pick a build
The first field is the build that holds the programs you want to trigger.
Add triggers
Click Create to add a trigger, then fill in:
- Emitter Name, required
- Program, required, filtered to the project's batch programs. Once picked, the program's connected database table shows read-only, a valid emitter program must watch a fixed table, a warning shows if the one you picked does not.
- Program Parameters, shown once a program with parameters is picked
- Debounce (ms), under Advanced, optional. Rapid changes within this window coalesce into a single run instead of firing the program once per change.
Add as many triggers as the deployment needs.
Datacenter and Performance Tier
Choose an existing datacenter or create one, then pick how much power it gets. See Deploy overview for what these two steps ask.
Finalize Details
Name the deployment and check the price in the footer, then click Create Emitter.
Once it exists
Use the deployment's Logs and Usage tabs to confirm triggers are firing as expected. Emitter has no Launch, Domain, Firewall, Analytics or User Assist tab.
Pricing
Emitter carries a flat $75/mo on top of the datacenter it runs on.