Docs
FALogin

Project settings

Settings tabs, changing the repository, domains, and build and CD options.

Settings tabs

On the project page, the Settings tab contains:
  • General — version, main file, readiness probe, and port.
  • Repository — repository and branch.
  • URLs — default URL and custom domains.
  • Envs — environment variables.
  • Build & CD — build location, npm registry, and deployment.
  • CORS — allowed origins and headers.
  • Advanced Setting — PHP and security settings.
For archive-backed projects, the Repository tab is hidden.

General

  • Version: the project stack version. Changing it creates a new pipeline.
  • Main file / Config directory: the main file or config directory, depending on the type.
  • Readiness probe URL: a path such as /health used to check whether the app is ready.
  • Port: the port the app listens on.
See Advanced settings for the full explanation.

Repository

  1. Click Change repository.
  2. Choose the Git account.
  3. Choose the new repository and branch.
  4. Click Save.
Environment variables, the port, and other settings are kept, and a new pipeline is created. A locked project cannot change its repository.

URLs

This tab shows the default Lexoya URL and the project's custom domains.
  • Add URL / Connect URL to connect a domain.
  • Manage Domains to manage all domains.
  • Edit to change the domain or certificate.
  • Disconnect to stop routing the domain.
The project must be running to add a domain. Each project supports up to 10 custom domains.
Full guide: Connecting a domain

Build & CD

Build location

Selects where the project is built. If builds fail in Iran because of sanctions, you can switch to Germany.
The Germany build location is only available for projects created in the Germany location.
Changing the build location creates a new pipeline.

npm Registry

Choose the platform default or a custom registry with an https URL. This only affects builds that install npm dependencies and applies from the next build.

Manual CD

When enabled, the project is not deployed automatically. The build runs, but you must click Deploy in the Pipelines tab to release the new version.

Auto Pipeline

When enabled, every push to the repository creates a new pipeline. This option is available for Git projects only.

Post-deploy command

An optional shell command run inside one ready pod after every successful deploy, for example migrations:
bash
php artisan migrate --force
If it fails, the failure is logged as a warning and does not fail the pipeline.

Other tabs