-
Notifications
You must be signed in to change notification settings - Fork 23
/
Copy path.env.example
104 lines (88 loc) · 3.09 KB
/
.env.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
PORT=3030
REMIX_APP_PORT=3030
NODE_ENV=production
RUNTIME_PLATFORM=docker-compose
V3_ENABLED=true
# TRIGGER_TELEMETRY_DISABLED=1
INTERNAL_OTEL_TRACE_DISABLED=1
INTERNAL_OTEL_TRACE_LOGGING_ENABLED=0
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_DB=postgres
DATABASE_HOST=postgres:5432
DATABASE_URL=postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${DATABASE_HOST}/${POSTGRES_DB}
# This sets the URL used for direct connections to the database and should only be needed in limited circumstances
# See: https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#fields:~:text=the%20shadow%20database.-,directUrl,-No
DIRECT_URL=${DATABASE_URL}
REDIS_HOST=redis
REDIS_PORT=6379
REDIS_TLS_DISABLED=true
# If this is set, emails that are not specified won't be able to log in
# WHITELISTED_EMAILS="authorized@yahoo\.com|authorized@gmail\.com"
# Accounts with these emails will become admins when signing up and get access to the admin panel
# ADMIN_EMAILS="admin@example\.com|another-admin@example\.com"
# If this is set, your users will be able to log in via GitHub
# AUTH_GITHUB_CLIENT_ID=
# AUTH_GITHUB_CLIENT_SECRET=
# E-mail settings
#
# - Ensure the FROM_EMAIL matches what you setup with Resend.com
# - If these are not set, emails will be printed to the console
#
# FROM_EMAIL=
# REPLY_TO_EMAIL=
# RESEND_API_KEY=
# Alert E-mail settings
# - Ensure the ALERT_FROM_EMAIL matches what you setup with Resend.com
# - If these are not set, email alerts will not work.
#
# ALERT_FROM_EMAIL=
# ALERT_RESEND_API_KEY=
# Concurrency limits
#
# - If these are too high, you may run out of resources on your worker. A simple fix is to either re-deploy
# with lower limits, or set appropriate limits in your trigger.config.ts or directly on your tasks.
#
DEFAULT_ORG_EXECUTION_CONCURRENCY_LIMIT=300
DEFAULT_ENV_EXECUTION_CONCURRENCY_LIMIT=100
# Secrets
#
# - You MUST change these in production!
#
# generate these with `openssl rand -hex 16`
MAGIC_LINK_SECRET=secret # used to encrypt magic link tokens
SESSION_SECRET=secret # used to encrypt session cookies
ENCRYPTION_KEY=ae13021afef0819c3a307ad487071c06 # used to encrypt permanent data
#
# generate these with `openssl rand -hex 32`
PROVIDER_SECRET=provider-secret
COORDINATOR_SECRET=coordinator-secret
# Worker settings
#
HTTP_SERVER_PORT=9020
COORDINATOR_HOST=127.0.0.1
COORDINATOR_PORT=${HTTP_SERVER_PORT}
REGISTRY_HOST=${DEPLOY_REGISTRY_HOST}
REGISTRY_NAMESPACE=${DEPLOY_REGISTRY_NAMESPACE}
# FORCE_CHECKPOINT_SIMULATION=0 # only uncomment if you are willing to try EXPERIMENTAL docker features - expect bugs
# Docker
#
# RESTART_POLICY=
# WEBAPP_PUBLISH_IP=
# TRIGGER_IMAGE_TAG=
# POSTGRES_IMAGE_TAG=
# REDIS_IMAGE_TAG=
# ELECTRIC_IMAGE_TAG=
# Registry settings
#
# - Images will be pushed to: host/namespace/project:version
#
# DEPLOY_REGISTRY_HOST=docker.io
# DEPLOY_REGISTRY_NAMESPACE=trigger # you should change this, for example to your Docker Hub username
# Domain settings
#
# - Should be uncommented unless you're just testing locally
# - Required for the split webapp / worker setup
#
# TRIGGER_PROTOCOL=https
# TRIGGER_DOMAIN=<your_subdomain>.ngrok-free.app