Prerequisites
Tools, infrastructure, and configuration prerequisites required before you deploy remoteEaze.
Last updated
This page covers everything an operator should have in place before attempting a deployment or a local source build.
Operator tools
| Tool | Required for | Notes |
|---|---|---|
Git | Source checkout, updates, auditing config | Required for source builds and normal repo-based operations |
Node.js 22.15.0+ | Local source build, PM2/manual runtime, local development | Matches the repo engine constraint |
pnpm 11.2.2 | Local source build and workspace operations | The repo uses pnpm only |
Docker | Dokploy and both Docker Compose paths | Required for containerized deployment |
Docker Compose | Compose-based deployment paths | Docker Desktop / Docker Engine Compose plugin is fine |
Infisical CLI | Workspace development scripts and Infisical-backed manual runtime | Not required for SKIP_INFISICAL=true compose paths |
Infrastructure prerequisites
Every real deployment needs:
| Dependency | Required | Purpose |
|---|---|---|
| PostgreSQL | Yes | Primary relational database |
| Redis | Yes | Queue backend, cache, locks, dashboards |
| S3-compatible storage | Yes | File uploads, downloads, and validation |
| Reverse proxy or domain routing | Yes | Public routing for web, API, and admin tools |
| DNS | Yes | Public hostnames and TLS issuance |
| Email provider | Yes in current runtime schema | Resend is the supported email path today |
If you are using a compose variant that includes postgres and redis, those services are created for you. If you are using PM2/manual runtime, you must provide PostgreSQL and Redis yourself.
Node and pnpm setup
The repo expects:
Node.js >= 22.15.0pnpm@11.2.2
Recommended local setup:
corepack enable
corepack prepare pnpm@11.2.2 --activateArcLocale package note
The web app and shared UI use:
@arc-laboratories/arclocale-compiler
That package is now published publicly on npm, so normal installs and Docker source builds do not require extra npm registry tokens or a special .npmrc.
ArcLocale and translation-provider keys
Normal deployment builds do not require translation-provider API keys.
The web build runs in ArcLocale cache-only mode, which means:
- deployment builds use committed translation cache
- no translation API calls are made during normal deployment builds
- builds fail if required translation cache entries are missing
Translation-provider keys are only needed when intentionally generating or refreshing translations in the translation workflow.
GHCR note
Registry-image deployment is supported.
If you use the GHCR-based deployment path, make sure the operator account or host has working ghcr.io pull credentials before deployment. If you prefer not to manage registry auth on the host, use the Docker Compose source-build path.
Infisical requirements
If you choose an Infisical-backed deployment path, you need:
- access to the correct Infisical project
- the correct environment slug, such as
dev,staging, orprod - separate service tokens for the services that use them
The Dokploy compose variant is Infisical-oriented. The source and registry compose variants can also use Infisical, but can be run without it when SKIP_INFISICAL=true.
Reverse proxy and DNS prerequisites
Before you route live traffic, decide:
- Your root app hostname, for example
remote-eaze.example.com - Whether you also want an API hostname, for example
api.remote-eaze.example.com - Which reverse proxy you will use
The docs include:
- a full Traefik example
- shorter path-focused Caddy and Nginx examples
See Routing and Domains.
Next step
Continue with Environment Reference.