|
| 1 | +# Default values are optimized for production to avoid having to configure |
| 2 | +# much in production. |
| 3 | +# |
| 4 | +# However it should be easy to get going in development too. If you see an |
| 5 | +# uncommented option that means it's either mandatory to set or it's being |
| 6 | +# overwritten in development to make your life easier. |
| 7 | + |
| 8 | +# Set this up to handle Github App configuration |
| 9 | +# GITHUB_APP_ID=12345 |
| 10 | +# GITHUB_CERT=Base64-encoded-private-key |
| 11 | + |
| 12 | +# Choose an admin email address and configure a mailer. If you don't specify |
| 13 | +# mailer details the local test adaptor will be used and mail previews can be |
| 14 | +# viewed at localhost:4000/dev/mailbox |
| 15 | +EMAIL_ADMIN='admin@openfn.org' |
| 16 | +# MAILGUN_API_KEY='some-key' |
| 17 | +# MAILGUN_DOMAIN='some-domain' |
| 18 | + |
| 19 | +# You should generate a random string of 64+ characters for this value in prod. |
| 20 | +# You can generate a secure secret by running: ./run secret |
| 21 | +SECRET_KEY_BASE=please_generate_a_more_secure_unique_secret_value_for_your_project |
| 22 | + |
| 23 | +# Which environment is running? MIX_ENV should be "dev" or "prod" and NODE_ENV |
| 24 | +# should be "production" or "development". When MIX_ENV is set to prod you'll |
| 25 | +# automatically be set to build and run releases instead of using mix. |
| 26 | +#MIX_ENV=prod |
| 27 | +#NODE_ENV=production |
| 28 | +MIX_ENV=dev |
| 29 | +NODE_ENV=development |
| 30 | + |
| 31 | +# Override the default log level |
| 32 | +# Must be a valid level, see: https://hexdocs.pm/logger/1.12.3/Logger.html#module-levels |
| 33 | +#LOG_LEVEL=debug |
| 34 | + |
| 35 | +# The URL that will be generated through out your app. When you combine all 3 |
| 36 | +# values it should be the URL that visitors access in their browser / client. |
| 37 | +#URL_SCHEME=https |
| 38 | +#URL_HOST= |
| 39 | +#URL_PORT=443 |
| 40 | +URL_SCHEME=http |
| 41 | +URL_HOST=localhost |
| 42 | +URL_PORT=4000 |
| 43 | + |
| 44 | +# If you're using a CDN you can customize which URL gets used for your static |
| 45 | +# files. If left commented out it will fall back to using your URL_HOST. |
| 46 | +#URL_STATIC_HOST= |
| 47 | + |
| 48 | +# The address and bind port for the web server. |
| 49 | +# (See: endpoint config in runtime.exs and Cowboy.) |
| 50 | +LISTEN_ADDRESS=0.0.0.0 |
| 51 | +PORT=4000 |
| 52 | + |
| 53 | +# The origins from which you want to allow requests (comma separated) |
| 54 | +ORIGINS=//localhost:* |
| 55 | + |
| 56 | +# You can configure error reporting via Sentry by providing a DSN. |
| 57 | +# SENTRY_DSN=https://some-url.ingest.sentry.io/some-id |
| 58 | + |
| 59 | +# ============================================================================== |
| 60 | +# <><><> JOB EXECUTION SETTINGS <><><> |
| 61 | + |
| 62 | +# You can configure the max run duration for jobs in milliseconds. This should |
| 63 | +# be lower than the pod termination grace period if using Kubernetes. |
| 64 | +MAX_RUN_DURATION=20000 |
| 65 | +MAX_DATACLIP_SIZE=10000000 |
| 66 | + |
| 67 | +# ------------------------------------------------------------------------------ |
| 68 | + |
| 69 | +# ============================================================================== |
| 70 | +# <><><> DATABASE SETTINGS <><><> |
| 71 | + |
| 72 | +# Disable SSL connections for Postgres |
| 73 | +# In production mode, SSL connections are enforced by default - uncomment to |
| 74 | +# disable this behaviour. |
| 75 | +#DISABLE_DB_SSL=true |
| 76 | + |
| 77 | +# You you're using Docker for postgres, set POSTGRES_USER and POSTGRES_PASSWORD |
| 78 | +# since the postgres Docker image uses them for its default database user and |
| 79 | +# password. The database URL will be composed from these variables: |
| 80 | +POSTGRES_USER=${DB_USER} |
| 81 | +POSTGRES_PASSWORD=${DB_PASSWORD} |
| 82 | +POSTGRES_HOST=db |
| 83 | +#POSTGRES_PORT=5432 |
| 84 | +POSTGRES_DB="lightning_${MIX_ENV}" |
| 85 | +DATABASE_URL="postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT:-5432}/${POSTGRES_DB}" |
| 86 | + |
| 87 | +# If you're not using docker, but running postgres locally and migrating/running |
| 88 | +# using `env $(cat .env | grep -v "#" | xargs )` set the database url directly: |
| 89 | +# DATABASE_URL=postgres://hello:password@localhost/lightning_dev |
| 90 | + |
| 91 | +# ============================================================================== |
| 92 | + |
| 93 | +# Generate secure keys, see ./DEPLOYMENT.md |
| 94 | +PRIMARY_ENCRYPTION_KEY=0bJ9w+hn4ebQrsCaWXuA9JY49fP9kbHmywGd5K7k+/s= |
| 95 | +ATTEMPTS_PRIVATE_KEY="LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb2dJQkFBS0NBUUVBeWJER3JEbFBWd05yWTA4czF3VkU5SktDSWhhditwT1ZXVSsyR2pSekFneEI5dW5CCjFrejdJQTh3SUIyZ1NseDhYWHlPZDA5QmhlMHBiRERxV2Q5YWV5OGZNb2tTMUVkcGFBT1k0YnRPYlIwbDFlM2wKazBQelBIc2lITWlFVWpTQm5yS2ZJZVJjd1VKK3NPaTQxVjYrTVV4V1FhSFBPTXRrWjRMNFdUOTVvV0paNG8wdQpQd0pXS0V0cmh3cHdoSldHeFl1Ym51TVhJdW1PTW5USFZ4cmlpdGRjODdyMDhuUTF3eDJjT3JkUkVBK25mWjVWCml6VHprUVFBTG1PNUI4V3IrS1ZYRW5HRUVHVTR2alRMYkQ5blAyclVXMXYvSFBTamgyZjlOaDlxd1RDQm04bGoKb1JBQ3BUTUhlS2VxYmpQOVgxM2V1bFp0a2hhK05kRndkeDdPZ1FJREFRQUJBb0lCQURrU2hkV2NUZ0F3WG9YMgpsSml2ekFodElOZm1sWnVSZ1pTSlF0MTlkQUhqV0JNM3FIc3N3MjhaL1NOSlh0OUw5b0U1eXRLbUljTjFEZUNvCm90Z1ZwUFB3cktKUE9YM0tTMkI4akJsc09GQVdER3ZSNnNIV1c1RUV3dTFrTEZWYXVFY2hBbmpEdHgrVTRtYkwKSStwMDZkcm5ZQTBvYll3RHVnQzBoZlF6U3diSVhaM3d6V25BVlRaZE4yTGFqRTA2UHRNSkxsSzZZZ3FyWmpObQpzeXpKSVgwRmg4WlFlOHZVMmF1U205UnIvTFhwMEN6TFpDYmxUT2RRcXlRdFQ3cHR5c2ZBUWZvZkkrMFNWcVZ2CkhqQUhaTU5ZZk9mSFJiMVBjVzFKdjZlSUJERFZiYXNCZVl5bWlQRStXVEpkOU1hbFNFSlI5NDFmaWFBQ1UwVEcKRlhLclQ4RUNnWUVBL0JaNEJvbkdONkVsQUd5akhldU42eXhka3JCUHJhUWh4am5ScEZxMGQzTjFISUdBS2pEVQpvQStEU0JzMG1NY2xRWm8yT1dHVTdZbzhwNkEzZVMyNTc2aVF6a1pndnNhS3hXcnFWTTBCRHdlOU5mdEYyVXQwCjhoczNZS1V2ek1yNEhiL1FTVFZkWldWZkR0YUdBY3kxTkFnVlRJcE9PK1FDTlk5V3p1cVVlT2tDZ1lFQXpOSVUKNm1HOGcxOUtqN1lJb3hmd1E1c3E1WGhWSk8zQ3MvVXpqSU5HKzNSRnZDWDRxd2VoTVdUY0NBVVFicnl5MGlJSApYdGpXR1B3clM5Z0JiZzdsS2VJdkdQYXRlZGhrZUNqMDJzVVp3SnZoUGowaHRXTnZWckRnb1doWG03M0xNUU1lCnRrOTdDejZta0J5RWw0VGcwMTVLL1JHK2hVLzl0aVhWRDBoUEtka0NnWUFqV0c4cDA0V0VaVWJQNFd1WmxWNkgKdStlKzJwUEJjQU1BVFRrVXgxY0liSnJlRFZaUUZCcXIrcURZcWwvY2tBZXNSQmdZUVpObEh2M1VMd1c0S3U0bwpLVVZzZHJlMzZCU3JDNHVocWtEY3Y2UUsvcGxUbDEzbFdHV1NXbmJ5U3Y4eEJLVUtycjNTcXIwQ1VwZmxock5kCmdVaWpPNzB1YnBEVXU2MWJRODdmaVFLQmdFQkhBYWRZaXNlVHBSdWFuZlZJOHU3VWlFN0JSNzh5R25OTlZTTVkKbzdNUUZ6NW5rRFZrVEpMcXV4Nk5NRTRBVEFJa0Nib2JSSDFNemUyY1dUNkgwQ1VueFc0SkpBSGtCZ3VybHNQOQpMUXJFSUpqZXFIQjdSeHFtb2FnbHpiQ2pqRnZTUmRZaTlWTmZFdmlRNm85K2RPd0FZSG94RW1CVjdTSTNsemlYCmtiaHBBb0dBYjBrVUVpanl0akZlUWJBRGYvRk92VlRVdmUxZW9PK3JuWmJ2V3NhVWhVSGRuMTdDUXc0Y1ZjK0UKbHQzWXhHVmMvNldIV3E3azB4YXBlVWJucEF4NjNIMTlNZTRjTmJFaXZSb2d4bzdHWERnRDIxbENGUHlCUmZKagpLN2g1VE1lQnRnZjhibGdrVzcxenkyWFdNWnBJRXVRT3ZCZjJqRVJuU0hYTDFrL2NObDQ9Ci0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg" |
| 96 | +WORKER_SECRET="dECXNlqctXJ/a+1FI4AaeLZY4Rp+Pxo23WwmJxC2xew=" |
| 97 | + |
| 98 | +# Start your app with RTM=false to manage your runtime manually. You might be |
| 99 | +# doing this so that you can run `ws-worker` by hand on a local branch, rather |
| 100 | +# than using the NPM installed version. |
| 101 | +# RTM=false |
| 102 | + |
| 103 | + |
| 104 | +# Should Docker restart your containers if they go down in unexpected ways? |
| 105 | +#DOCKER_RESTART_POLICY=unless-stopped |
| 106 | +DOCKER_RESTART_POLICY=no |
| 107 | + |
| 108 | +# What health check test command do you want to run? In development, having it |
| 109 | +# curl your web server will result in a lot of log spam, so setting it to |
| 110 | +# /bin/true is an easy way to make the health check do basically nothing. |
| 111 | +#DOCKER_WEB_HEALTHCHECK_TEST=curl localhost:4000/health_check |
| 112 | +DOCKER_WEB_HEALTHCHECK_TEST=/bin/true |
| 113 | + |
| 114 | +# What ip:port should be published back to the Docker host for the app server? |
| 115 | +# If you're using Docker Toolbox or a custom VM you can't use 127.0.0.1. This |
| 116 | +# is being overwritten in dev to be compatible with more dev environments. |
| 117 | +# |
| 118 | +# If you have a port conflict because something else is using 4000 then you |
| 119 | +# can either stop that process or change 4000 to be something else. |
| 120 | +# |
| 121 | +# Use the default in production to avoid having it directly accessible to |
| 122 | +# the internet without assistance from a cloud based firewall. |
| 123 | +#LIGHTNING_EXTERNAL_PORT=127.0.0.1:4000 |
| 124 | +LIGHTNING_EXTERNAL_PORT=4001 |
| 125 | + |
| 126 | +# What volume path should be used? In dev we want to volume mount everything |
| 127 | +# so we can develop our code without rebuilding our Docker images. |
| 128 | +# Note that by mounting the whole project into the container, you will need to |
| 129 | +# follow the Contributing steps in the README. |
| 130 | +#LIGHTNING_VOLUME=.:/app |
| 131 | + |
| 132 | +# What CPU and memory constraints will be added to your services? When left at |
| 133 | +# 0, they will happily use as much as needed. |
| 134 | +#DOCKER_POSTGRES_CPUS=0 |
| 135 | +#DOCKER_POSTGRES_MEMORY=0 |
| 136 | +#DOCKER_WEB_CPUS=0 |
| 137 | +#DOCKER_WEB_MEMORY=0 |
| 138 | + |
| 139 | +# Give this variable the value of true if you want the system to create a sample project for a new registered user |
| 140 | +INIT_PROJECT_FOR_NEW_USER=false |
| 141 | + |
| 142 | +# If not provided, PURGE_DELETED_AFTER_DAYS defaults to 7. Set to 0 to never purge deleted records. |
| 143 | +PURGE_DELETED_AFTER_DAYS=7 |
| 144 | + |
| 145 | +# To use https://plausible.io/ analytics, provide the SRC for your script and |
| 146 | +# your data-domain below. |
| 147 | +# PLAUSIBLE_SRC=https://plausible.io/js/script.js |
| 148 | +# PLAUSIBLE_DATA_DOMAIN=openfn.org |
| 149 | + |
| 150 | +# If you wish to enable PromEx-driven Prometheus/Grafana monitoring use the following: |
| 151 | +# PROMEX_ENABLED=true |
| 152 | +# PROMEX_GRAFANA_HOST=http://localhost:3000 |
| 153 | +# PROMEX_GRAFANA_USER=admin |
| 154 | +# PROMEX_GRAFANA_PASSWORD=admin |
| 155 | +# PROMEX_UPLOAD_GRAFANA_DASHBOARDS_ON_START=true |
| 156 | +# PROMEX_DATASOURCE_ID=promex |
| 157 | +# PROMEX_METRICS_ENDPOINT_AUTHORIZATION_REQUIRED=yes |
| 158 | +# PROMEX_METRICS_ENDPOINT_TOKEN=foobar |
| 159 | +# PROMEX_ENDPOINT_SCHEME=http |
| 160 | + |
| 161 | +# The length of time an Attempt must remain in the `available` state before it is |
| 162 | +# considered `stalled`. |
| 163 | +# METRICS_STALLED_ATTEMPT_THRESHOLD_SECONDS=300 |
| 164 | + |
| 165 | +# The maximum age of an Attempt that will be considered when measuring |
| 166 | +# Attempt performance. |
| 167 | +# METRICS_ATTEMPT_PERFORMANCE_AGE_SECONDS=120 |
| 168 | + |
| 169 | + |
| 170 | + |
| 171 | +# Example .env copied from Lightning repository, full description of variables can be found in |
| 172 | +# https://github.com/OpenFn/Lightning |
| 173 | + |
| 174 | +# Thise secrets should be regenerated |
| 175 | +PRIMARY_ENCRYPTION_KEY=0bJ9w+hn4ebQrsCaWXuA9JY49fP9kbHmywGd5K7k+/s= |
| 176 | +SECRET_KEY_BASE=please_generate_a_more_secure_unique_secret_value_for_your_project |
| 177 | + |
| 178 | + |
| 179 | +IMIS_USER_FIRST_NAME=IMISUser |
| 180 | +IMIS_USER_LAST_NAME=IMISUser |
| 181 | +IMIS_USER_PASSWORD=IMISUserPassword |
| 182 | +IMIS_USER_EMAIL=IMISUser@openimis.com |
| 183 | +IMIS_DB_HOST=db |
| 184 | +IMIS_DB_PORT=5439 |
| 185 | +IMIS_DB_DATABASE=IMIS |
| 186 | +IMIS_DB_USER=IMISUser |
| 187 | +IMIS_DB_PASSWORD=IMISUserPassword |
0 commit comments