Intlayer CLI Init Infra Command

Description

The init infra command sets up the Intlayer infrastructure on your machine. It downloads the hosted installer for your platform (https://intlayer.org/install.sh on macOS / Linux, https://intlayer.org/install.ps1 on Windows) and runs it with your terminal attached, so the installer's own menu and progress output reach you unchanged.

The installer asks how you want to run Intlayer:

• Desktop app: downloads the native dashboard for your OS and CPU and opens or installs it. The desktop build talks to the Intlayer Cloud backend.
• All-in-one Docker: dashboard + API + MongoDB + Redis + MinIO in a single container backed by one volume. Writes ./intlayer.env with the secrets generated and pulls the intlayer/cms-all image.
• Docker Compose: one container per service, for scalable self-hosting. Writes docker-compose.yml and .env into ./intlayer/ and pulls the images.

The hosted installer is the single source of truth for the setup flow: the CLI runs it rather than re-implementing the same steps, so npx intlayer init infra and curl -fsSL https://intlayer.org/install.sh | sh do exactly the same thing.

Usage

npx intlayer init infra [options]

The same step is offered from the checklist of npx intlayer init --interactive, under Infrastructure (desktop app / self-hosting).

Options

• -m, --mode <mode> - Optional. Skip the installer's menu and run one mode directly. Accepted values: desktop, docker (all-in-one) or compose. Any other value exits with an error listing the accepted modes.

Examples

Pick the mode interactively

npx intlayer init infra

Install the desktop app

npx intlayer init infra --mode desktop

Self-host with the all-in-one container

npx intlayer init infra --mode docker

Self-host with Docker Compose

npx intlayer init infra --mode compose

Example output

npx intlayer init infra --mode compose
◇  Installer downloaded
▸ Fetching docker-compose.yml into ./intlayer
▸ Writing ./intlayer/.env

  Let's fill in .env. Press Enter to accept a suggestion;
  every value can be changed later in the file.

? Domain Intlayer will be served on (empty = localhost only):

  How should Intlayer send emails? The first account cannot be verified
  without a working mailer.

    1) Resend            API key from resend.com
    2) SMTP relay        Your own SMTP server
    3) Later             Fill in the file by hand before starting

? Choice [1-3]: 1
? Resend API key:
? Sender address [Intlayer <no-reply@example.com>]:
? OpenAI API key, enables AI translation (empty = skip):
▸ Pulling images

  Everything is installed.

  1. Start the stack:

       cd ./intlayer && docker compose up -d

  Then open http://localhost:3000
  First boot initialises the datastores, so give it a minute. The first
  account you create becomes the super admin.

    Logs      docker compose logs -f
    Stop      docker compose down
    Upgrade   docker compose pull && docker compose up -d

Given a domain (for instance example.org), the installer suggests https://cms.example.org, https://back.example.org and https://s3.example.org/intlayer for the dashboard, the API and the object storage, writes them to the environment file, and switches the start command to a build from the repository, since the published dashboard image only works on localhost. See Custom domain.

Installer settings

The installer reads a few environment variables, which the CLI passes through untouched. Set them in your shell before running the command:

INTLAYER_COMPOSE_DIR=./cms npx intlayer init infra --mode compose

The port variables only change the host side of the mapping. The published images have http://localhost:3000, http://localhost:3100 and http://localhost:9000 compiled into the dashboard bundle, so keep the defaults unless you build your own images: see the self-hosting guide.

Requirements

• Desktop app needs Node.js: the app embeds the dashboard's server and starts it with the machine's own node binary.
• Docker modes need Docker (Docker Desktop with the WSL 2 backend on Windows). The Compose mode also needs the docker compose plugin.

Notes

• Re-running the command is safe: an existing environment file is never overwritten, so it doubles as the upgrade path (the installer pulls the latest images and keeps your secrets).
• The installer is downloaded to a temporary directory and deleted once it exits, whatever the outcome.
• The command's exit code is the installer's. If the download itself fails, the CLI prints the equivalent curl … | sh (or irm … | iex) command so you can run the installer directly.
• The Docker modes need a mailer to send sign-in emails. The installer asks for one; if you skip the question (or run without a terminal, where the questions are skipped altogether), configure Resend or SMTP in the generated environment file: see Global mailer.

Related