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.
MolternFull-stack hosting
Solutions
Keep the frontend, backend and data connected.
Run web applications and supporting services in an environment your team can understand.
Flight paths artwork / 11
A full-stack app has more to it than the interface. Configure the backend runtime, attach the services it needs and keep sensitive values out of the repository. Use the deployment history and logs to understand what changed when a release needs attention.
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.
Check the release people will use
Inspect deployment status and logs, verify the URL and test the application’s main workflow. Record who owns configuration changes, service upgrades and recovery.
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.
What should I check when a deployment fails?
Start with deployment logs, build commands, runtime port, health checks and required variables, then follow the troubleshooting guide.
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 ↗