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
Getting startedQuickstart

Quickstart: deploy your first application

This tutorial takes you through the complete customer workflow. You need an Infralane account, an active workspace and project, and either a Git repository or a ready-made image.

Before you begin

Prepare the following:

  • a short application name, such as customer-api;
  • the port your web service listens on, if it accepts web traffic;
  • the build and start commands used by the project, for a Git deployment;
  • required environment variable names and values;
  • an estimate of the CPU, memory, and persistent storage the app needs.

For a connected private repository, connect GitHub first under Workspace → Integrations.

Select the workspace and project

Use the selectors in the dashboard navigation to confirm the active workspace and project. Every resource created in the next steps belongs to that selection.

Create a resource pool

Open Resource Pools and select Create resource pool. Enter a recognizable name, then select CPU, memory, storage, and region.

Review the monthly estimate and the configuration summary. Select Create resource pool. Creation happens asynchronously, so return to the pool list and wait until the pool is active before depending on it for production traffic.

Open the application launchpad

Open Applications and select Deploy application. The launchpad has five steps: source, type and build, resources, runtime configuration, and review.

Choose a source

Enter the application name and an optional description.

For GitHub, choose either a repository from the connected account or Public repository URL. Confirm the branch and, for a monorepo, set the root directory that contains the application.

For an image, choose Docker Image and enter the complete image reference, including a tag when you need a specific release.

Describe how the application runs

Choose Web Service, Static Site, or Background Worker.

For source builds, select the language runtime and verify the suggested commands. Web services need a start command and port. Static sites need an output directory. Workers do not use a public port.

Allocate resources

Choose the active resource pool, then select a preset or enter CPU and memory manually. Make sure the allocation fits within the pool alongside its other applications.

Add runtime configuration

Add environment variables and persistent volumes only when the application needs them. Each volume needs a name, a mount path inside the app, and a size.

Never paste a secret into a description, command, or other public field.

Review and deploy

Read the deployment summary from top to bottom. Pay particular attention to source, branch or image tag, application type, port, resource pool, CPU, memory, and runtime values.

Select Deploy app. Infralane opens the new deployment so you can follow its state.

Verify the release

Wait for the deployment to become Live. Then:

  1. open the application overview;
  2. confirm the public endpoint, when one is assigned;
  3. open Logs and check for startup errors;
  4. test a small, safe request against the application;
  5. keep the deployment page open until health and behavior are confirmed.

A Live deployment tells you the release completed. You should still test the application’s important user paths and check its logs before announcing a production change.

If the deployment fails

Open the failed deployment and read the last meaningful error. Common causes are a wrong branch or image reference, an incorrect build or start command, a missing runtime value, a wrong port, or an application that exits during startup. See Troubleshoot deployments.

Last updated on