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
Logs and terminalApplication terminal

Application terminal

The Terminal tab opens an interactive command session inside an active application instance. Use it for focused diagnosis, not as the normal way to configure or release an application.

Terminal access is powerful. Commands can change files, reveal runtime data, interrupt the app, or damage persistent data. Use the least privilege available and avoid terminal access on production unless it is necessary.

Open a session

Verify context

Confirm the workspace, project, application name, and environment. If this is production, state the reason for access in your team’s incident or change record.

Open Terminal

Select the application’s Terminal tab. The status changes from Connecting to Connected when the session is ready. An active deployment is required.

Run a read-only check first

Start with commands that inspect state without modifying it. Avoid printing environment values or reading files likely to contain credentials.

Close the page when finished

Closing or leaving the page ends the session. Confirm the application remains healthy and review logs for unexpected effects.

Safe operating rules

  • do not paste secrets into command arguments where they may be recorded;
  • do not install permanent fixes manually in a running instance;
  • make durable changes in source code or application settings and redeploy;
  • do not delete files or data without a verified backup and an approved recovery plan;
  • never copy private runtime data into a support ticket;
  • prefer the application’s normal administrative tools for data changes.

Connection errors

If the terminal cannot connect, confirm the application has an active deployment, select Try again, and check application logs. A failed or still-pending deployment may not have an available session.

Why manual changes do not belong in the terminal

An interactive change can be lost when the application is redeployed or replaced. It is also harder for teammates to review and reproduce. Use the terminal to learn what is wrong; use versioned source and dashboard configuration to fix it.

Last updated on