doover-cloud-apps

Cloud processors run serverless logic in response to channel messages or schedules. Implement event handlers like on_message_create in Python, package your code into a deployment zip with a doover_config.json, then deploy to Doover. The platform manages scaling and execution automatically.

Yes. Integration apps receive data through HTTP endpoints or scheduled triggers. Implement on_ingestion_endpoint handlers in Python, configure triggers in doover_config.json, package into a deployment zip, and deploy. Doover handles routing and scheduling across your organization.

You need Python runtime tooling, a packaging script to create a deployment zip, and a doover_config.json file to configure your app's handlers and triggers. The Skill provides end-to-end patterns for packaging and deployment within your Doover organization.

Processor apps contain cloud logic for devices and react to channel messages or schedules. Integration apps ingest external data via HTTP endpoints or scheduled tasks. Both run serverless and use the same Python handler pattern and deployment workflow.

No. Doover handles all infrastructure and scaling. You write Python handlers, configure triggers in doover_config.json, and package your code. The platform manages execution, scaling, and event routing automatically.

Yes. Both processor and integration apps support scheduled triggers. Define schedule configurations in doover_config.json, implement the corresponding handler, package the app, and deploy. Doover executes handlers on your specified schedule.