Nango requires a NANGO_ENCRYPTION_KEY. Once you create this, it cannot be edited.
Here's an overview of the important environment variables when deploying to production. Make sure to review all of these in your .env file.
NANGO_ENCRYPTION_KEY=<nango_encryption_key># Replace these with your <vm_external_ip> in production!NANGO_SERVER_URL=http://<vm_external_ip>:3050NANGO_PUBLIC_CONNECT_URL=http://<vm_external_ip>:3051# Modify these in production environments!NANGO_DASHBOARD_USERNAME=admin@example.comNANGO_DASHBOARD_PASSWORD=adminADMIN!@12
Build and deploy SigNoz, Nango, OTEL Collector, and Jaeger:
Here's an overview of the important environment variables when deploying to production. Make sure to review all of these in your .env file.
ENVIRONMENT=production# AI Provider Keys (you need at least one)ANTHROPIC_API_KEY=OPENAI_API_KEY=GOOGLE_GENERATIVE_AI_API_KEY=AZURE_API_KEY=# From Nango dashboard at http://<vm_external_ip>:3050NANGO_SECRET_KEY=# From SigNoz dashboard at http://<vm_external_ip>:3080SIGNOZ_API_KEY=# Set these for the Manage UI at http://<vm_external_ip>:3000PUBLIC_INKEEP_AGENTS_API_URL=http://<vm_external_ip>:3002PUBLIC_NANGO_SERVER_URL=http://<vm_external_ip>:3050PUBLIC_NANGO_CONNECT_BASE_URL=http://<vm_external_ip>:3051PUBLIC_SIGNOZ_URL=http://<vm_external_ip>:3080# Set these to access Manage UI at http://<vm_external_ip>:3000INKEEP_AGENTS_MANAGE_UI_USERNAME=admin@example.comINKEEP_AGENTS_MANAGE_UI_PASSWORD=# Generated with: openssl rand -base64 32INKEEP_AGENTS_JWT_SIGNING_SECRET=BETTER_AUTH_SECRET=SPICEDB_PRESHARED_KEY=INKEEP_AGENTS_TEMP_JWT_PRIVATE_KEY=INKEEP_AGENTS_TEMP_JWT_PUBLIC_KEY=
Tip
For long-running agents or custom deployment requirements, you can override runtime limits like execution timeouts, maximum transfers, and generation steps. See Configure Runtime Limits for examples and the complete list of overridable settings.
Run with Docker:
docker compose up -d
Then open http://<vm_external_ip>:3000 in a browser!