Email and Notifications

remoteEaze currently uses Resend for outbound email delivery.

Required variables

RESEND_API_KEY=
RESEND_FROM_EMAIL=
REMOTE_EAZE_DISABLE_OUTBOUND_EMAIL=false
FRONTEND_URL=

FRONTEND_URL matters because many emails include links back to the web application.

What each setting does

Resend setup

Recommended references:

• Resend API introduction
• Resend Domains

Minimum setup

1. Create a Resend account or team.
2. Add and verify the sender domain.
3. Create an API key.
4. Set RESEND_FROM_EMAIL to an address on the verified domain.

Disable mode

Set this when you want the app to execute notification flows without sending real emails:

REMOTE_EAZE_DISABLE_OUTBOUND_EMAIL=true

Use cases:

• internal demos
• local testing
• environments where templates must be exercised without live delivery

Testing email output

The repository includes a helper script:

pnpm email:test -- --list
pnpm email:test -- --template AUTH.INVITE --to you@example.com
pnpm email:test -- --template COB.ERROR --dry-run --write-html /tmp/cob-error.html

The script can:

• list available templates
• send a real email
• render previews without sending
• write generated HTML to disk for review

Notifications versus email

Not every notification concern is the same:

• in-app notifications still exist even if outbound email is disabled
• email is one delivery channel
• other notification flows may still enqueue or render successfully even when email sending is turned off

Operational advice

For production:

1. verify the sender domain before go-live
2. use a non-personal sender address
3. test at least one auth email and one operational email template
4. decide whether non-production environments should use disable mode

Next step

Choose your deployment path:

• Dokploy and Traefik
• Docker Compose: Source Build
• Docker Compose: Registry Images
• PM2 and Manual Runtime