Local Development

This page is about running remoteEaze on a local machine for development rather than deploying it to a shared server.

Two practical local paths

Workspace development path

Use this when you want the normal source-code inner loop with local editors and live app code.

What it needs:

• Node.js
• pnpm
• PostgreSQL
• Redis
• source checkout
• Infisical CLI for the normal workspace dev scripts

Local compose path

Use this when you want a more deployment-like local stack on your machine.

What it needs:

• Docker
• Docker Compose
• source checkout

Important Infisical note

The normal workspace dev scripts for the API and queue packages call infisical run.

That means:

• the standard workspace dev path expects the Infisical CLI
• compose-based local stacks can bypass Infisical with SKIP_INFISICAL=true

If you do not want Infisical in local development, the easiest path is usually:

• docker-compose.source.yml with SKIP_INFISICAL=true

Local env basics

The root .env file is still the main local env source for the repo.

At minimum, local development commonly needs:

DATABASE_URL=postgresql://user:password@localhost:5432/remote_eaze
REDIS_URL=redis://localhost:6379
BETTER_AUTH_SECRET=change-me-minimum-32-chars
BETTER_AUTH_URL=http://localhost:3000
ENCRYPTION_KEY=change-me-minimum-32-chars
ENCRYPTION_SALT=change-me-minimum-16-chars
LICENSE_SECRET_KEY=change-me-minimum-32-chars
RESEND_API_KEY=re_test
RESEND_FROM_EMAIL=noreply@example.com
FRONTEND_URL=http://localhost:5173
STORAGE_ENDPOINT=http://localhost:8333
STORAGE_BUCKET=remote-eaze-dev
STORAGE_ACCESS_KEY=...
STORAGE_SECRET_KEY=...

Native and emulator-specific local values

Common additions for native-shell or emulator work:

ADDITIONAL_TRUSTED_ORIGINS=http://10.0.2.2
VITE_BACKEND_URL=http://10.0.2.2:3000

Use capacitor://localhost when you are developing inside a Capacitor shell that uses that origin.

Testing-only envs

These are not normal runtime envs. They are for integration-style test harnesses.

INTEGRATION_DATABASE_URL=postgresql://user:password@localhost:5432/remote_eaze_integration
INTEGRATION_REDIS_URL=redis://localhost:6379/1

Use separate resources for these values. The test harnesses are intentionally cautious and expect isolated integration targets.

When to use local compose instead

Use the local compose path when:

• you want a more deployment-like environment on your workstation
• you do not want to rely on the Infisical CLI for normal startup
• you want the compose file to create Postgres and Redis for you

Relevant files:

• docker-compose.source.yml
• docker-compose.registry.yml

Next step

For observability setup, continue with Telemetry and Monitoring.