Source and deployment target
Settings controls which repository branch Infrastry deploys and where the application runs. Review these values before launching a release from a different branch or moving the application to another target.
- Repository identifies the connected source for the application.
- Branch selects the line of development used by future deployments.
- Runtime and region describe where the production plan will run.
Environment values and secrets
Use Environment to add the configuration your application reads while it runs. Mark credentials, tokens, and other sensitive values as secret.
- Use clear uppercase names that match the variables expected by your application.
- Secret values are not shown again after they are saved.
- Deploy the application again after changing a value so the new runtime receives it.
Note: Do not place passwords or access tokens in the repository. Store them as secret environment values instead.
The app spec
The app spec is Infrastry’s provider-neutral description of your application. It connects the source code to the components, commands, network ports, health checks, and dependencies used for deployment.
- Review the visual summary for a quick view of each detected component.
- Use the JSON view when you need the exact generated configuration.
- Compare revisions to understand how a new analysis changed the plan.
Persistent storage
Volumes keep application data beyond the lifetime of one runtime. Infrastry can also prepare persistent database storage when repository analysis identifies that the application needs it.
- Open Volumes to see retained storage and where it is mounted.
- Stopping or replacing a runtime keeps retained volume data.
- Confirm the application writes durable data to the configured mount rather than temporary runtime storage.