Deploy the code you own
Connect a repository and branch, review the build and start commands, then set the runtime port and health check. Static sites and web services have different operating needs.
MolternDevelopers
For your team
Your code. A clearer path to production.
Deploy a Git-backed web service or static site, connect private services and follow the release from one workspace.
Flight paths artwork / 03
Keep the repository and framework you already use. Set the build, runtime port and health check, then inspect the deployment logs. Add databases and other services through explicit connections instead of turning each environment into a collection of copied credentials.
Put it into practice
Connect data privately
Put the service in the appropriate environment and use explicit private connections where supported. Keep server credentials out of browser code and source control.
Separate test work from production
Organize development, preview, staging and production work explicitly. Review the variables and connected services for each environment rather than assuming they share data.
Detailed instructions are maintained in the product documentation.
Questions before you start
Can I keep my existing framework?
Use a supported runtime or a Dockerfile. Review the application guide for your build output and server requirements.
Who owns backups and recovery?
Name an owner and review the service-specific persistence and recovery instructions before relying on its data.
Does a preview copy production data?
Do not assume it does. Configure appropriate test services and verify which data and variables the preview can access.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗