Skip to Content
We are conducting a survey to learn how startups, SMEs, developers, and technical teams currently host, deploy, and operate software. Take the survey
Infralane
Infralane
ApplicationsManage an application

Manage an application

Open an application from Applications to see its current source, runtime, resource allocation, public endpoint, and release history.

Overview

The overview shows the runtime, CPU, memory, port, source, branch, working directory, resource pool, commands, runtime-data counts, and public endpoint. Use it as a read-only verification page after creation or a configuration change.

Open the public application

When a public endpoint is assigned, select Open application. Test a safe user path and verify that the endpoint belongs to the intended environment. An application without an endpoint directs you toward logs instead.

Change settings

Settings are divided into sections:

  • General — description; the application name is permanent.
  • Source and build — Git or image source, branch, root directory, application type, commands, output directory, runtime, and port as applicable.
  • Resources — resource pool, CPU, and memory.
  • Runtime data — environment variables and persistent volumes.

Save one section at a time. Every saved section starts a new deployment. A successful save does not by itself prove the new release is healthy.

Open Settings

Choose the section containing the value you need to change.

Make one coherent change

Keep changes small enough to understand and verify. The page marks sections with unsaved changes.

Review sensitive fields

Keep environment values masked unless you must inspect one. Make sure no secret is visible before sharing the screen.

Save the section

Use that section’s save action. If the save succeeds, a new deployment starts. If settings save but deployment fails, the dashboard warns you to inspect deployment logs.

Verify the new deployment

Open Deployments, select the newest entry, and watch its status. Then check Logs and test the application.

Move an application to another pool

Change the resource pool only after confirming that the destination pool is active and has sufficient free CPU, memory, and storage. Treat the move as a production change and verify the resulting deployment.

Unsaved changes

The settings page warns when a section differs from the saved configuration. Use Reset for a section when you want to discard those edits. Avoid navigating away until you intentionally save or reset them.

Last updated on