Docs
FALogin

Create a project

Step-by-step guide to creating a project on the cloud platform, from source to resources and build.

Before you start

  • A connected Git account for a Git source.
  • Or a project archive as zip, tar.gz, or tgz, up to 500 MB.
  • Enough balance for the project's hourly cost.

Start creating

On the Projects page, click Create Project. The wizard has six steps: Source, Project type, Settings, Variables, Plan, and Review.

Step 1: Project source

Three options are available:
  • Git repository: choose a GitHub, GitLab, or Gitea account, then the repository and branch.
  • Upload archive: select a zip or tar.gz file or drop it into the box.
  • Ready image: not available yet; marked Coming Soon.
If you have no Git account, click Add Git Account. Only repositories you have admin access to are listed.
For Git, the default branch is selected. Click the branch name to choose another one.
For an archive, wait until the status shows Uploaded before continuing.

Step 2: Project type

  1. Lexoya detects the project language and suggests a type.
  2. Choose the project type.
  3. Choose the version from that type's list.
If your type is not listed, choose Docker with your own Dockerfile and provide the Dockerfile.
The project type cannot be changed after creation, but the version can be changed later in settings.

Step 3: Build settings

  • Application port: if it is detected from the Dockerfile or project type, the detected value is used. Your app must listen on this port.
  • Main file / Dockerfile / config directory: choose the required file or directory for the type. If the path is not listed, type it manually.
  • File status: Lexoya checks the required files and lists anything missing.
For an uploaded project, the build root inside the archive is detected automatically; enter the main file path inside the archive.

Step 4: Environment variables (optional)

Enter variables row by row or in text mode. In text mode, each line is KEY=value.
  • Variables are available at build time and at runtime.
  • Put secrets here, not in the repository.
  • Variables are visible to project team members.
  • Values must not contain " or end with \.
See Environment variables for details.

Step 5: Resources and plan

Choose the starting resources:
ResourceOptions
CPU0.5, 1, 2, or 4 cores
Memory512 MB, 1, 2, or 4 GB
Billing is hourly, and the monthly equivalent is shown on the same screen. Coupons are applied here as well.
Low resources can slow down or stop your app. If you are unsure, choose 1 core and 1 GB.
You can change resources later from Plan on the project page.

Step 6: Review and build

  1. Check the project name and edit it if needed.
  2. Review the source, Git account, location, port, resources, and estimated build time.
  3. Click Create Project.
The project enters the build queue and usually takes 2–4 minutes. When it finishes, you are taken to the project page.
If your balance is insufficient, the project stays in Insufficient balance until you top up.

After creation

Related