Deploy your first application
Create an application, connect source, configure, deploy, reach it, check its health and clean up.
Who this is for: developers deploying a web service on id0n for the first time. What you get: a running HTTP service with its own URL, health checks and logs.
Prerequisites
- Access to id0n. See Account access.
- A service that listens for HTTP requests, in a Git repository or a container image.
- Credentials for the repository or registry, if they are private.
Available at release
This page describes how Runtime behaves. Exact Console paths and command-line syntax are added when the customer interface reference is published.
Create an application
An application is the unit Runtime builds, runs and routes to. Give it a name that is unique within your account.
Connect source or an image
Connect the repository and branch to deploy. If the repository is private, add a credential scoped to this application. Runtime only uses that credential for this application.
Configure
- Set environment variables, marking sensitive values as secrets.
- Choose capacity: CPU, memory and disk.
- Confirm the port your service listens on.
Deploy
Start a deploy. Runtime fetches the source, builds it on id0n build workers, runs health checks and then sends traffic to the new release.
Reach the service
Open the application's URL. To use your own domain, see Domains and TLS.
Check health and logs
Confirm the deploy succeeded and the service is healthy. If it failed, read the build output and the failed-deploy logs. See Logs and diagnosis.
Clean up
If this was a test, delete the application. Deleting an application removes its releases, configuration and routing.
Verify success
- The latest deploy shows as successful.
- The application URL responds.
- Health checks pass and the process is running.
Common failures
| Symptom | Likely cause | See |
|---|---|---|
| Source fetch fails | Missing or wrongly scoped credential | Source and image access |
| Build refused before it starts | An unsupported build setting, such as a custom cache | Unsupported features |
| Deploy never takes traffic | Health checks fail, or the service listens on a different port | Health checks |
Did the deploy fail? Go to Troubleshooting.