Deploying a Generated App
Applies to: App Generation projects that use the SaaS Engine template
AppWizzy deploys the initial generated application to a hosted development environment. Creation and initial deployment run as one managed process.
Deployment is different from VM provisioning. It builds and starts the generated application inside its hosted environment.
Initial deployment
After requirements gathering, AppWizzy performs these actions:
- It creates the project and hosted environment.
- It generates the initial application schema.
- It creates the application source code.
- It deploys the development application.
- It opens the editor while progress continues.
The project can show an in-progress state until the application is ready. Do not start a duplicate project because the first deployment needs time.
Development environment
The development environment is the current workspace for generation, editing, and testing. The application preview uses this environment.
Use Edit via Chat or Code Editor to make changes. Review the application after each completed change.
The project VM must be running before the application URL, editor tools, or SSH can work.
Review deployment status
The project shows recent deployments with their start time, duration, environment, and status.
Open View Build Log to inspect one deployment. The log can identify dependency, build, startup, or application errors.
Record the deployment time and exact error before you contact support. Read Activity and Logs for log types.
Deploy again
The project can show Deploy when the development application is not running or has an error.
Use it after you correct the cause of a failed development deployment. Do not redeploy repeatedly without reviewing the latest error.
A deployment operation can consume credits. Review the displayed action and your billing transactions.
Stable environment status
Manual Deploy to Stable and Sync to Stable controls are currently disabled. Do not plan a workflow that depends on these controls.
Some existing projects can have stable environment records or URLs. Their presence does not make manual stable deployment available.
AppWizzy will update this page when the stable deployment workflow becomes available again.
Publish and custom domains
Application deployment and domain publication are separate operations. A custom domain does not build or repair the application.
Publish controls appear only when the required project environment and permissions are available.
Test the application through its AppWizzy URL before you connect or publish a custom domain.
Deployment does not replace backups
A deployment does not create a complete VM backup. A saved project version is also not a complete system backup.
AppWizzy creates daily backups of hosted VM systems. Read Data Persistence and Backups for scope and restoration.
Troubleshoot a failed deployment
- Confirm that the VM is running.
- Check the latest deployment status.
- Open the build log.
- Review the last source or schema change.
- Correct the reported error.
- Deploy the development application again when the control is available.
Do not use Drop DB and Rebuild as a general deployment repair. That action can delete generated application data.
Read Troubleshooting AppWizzy Projects for the general diagnostic process.