deployment

To configure deployment settings, you define required frontage metadata like name and description, then specify a deployment target such as autoscale or vm along with optional run and build commands to generate an actionable production configuration.

Available deployment targets include autoscale, vm, scheduled, and static, allowing you to fit various project types like websites, bots, or scheduled services into your production publishing workflow.

Yes, you can configure publishing workflows for scheduled tasks and bots by selecting the scheduled deployment target, which validates target-specific behavior and generates the necessary configuration to run your service.

Optional parameters include run, build, and publicDir, which guide how to execute and compile your project to ensure target-specific behavior is validated before generating the final deployment configuration.

The best way to publish a static website is to select the static deployment target, configure any optional publicDir parameter, and let the workflow validate your settings to generate an actionable deployment configuration.

Choose autoscale when your project requires dynamic scaling for varying traffic, and select vm when you need a dedicated virtual machine environment, ensuring the target-specific behavior matches your production run requirements.