-
Notifications
You must be signed in to change notification settings - Fork 0
/
.env.production
91 lines (72 loc) · 4.5 KB
/
.env.production
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
# production settings for rinkeby
####################################################
######### Global settings
####################################################
# see https://ulog.js.org/ modules: ratesFeeder, TickerProvider, statusApi, MatchMaker, EthereumConnection
LOG = LOG
# valid values: http, websocket NB: Infura Websocket is not working anymore (new V3 websocket API is not supported yet)
PROVIDER_TYPE = websocket
# infura: https://rinkeby.infura.io/v3/ (with trailing slash) or wss://rinkeby.infura.io/ws/v3/
# local: http://localhost:8545 or ws://localhost:8545
PROVIDER_URL = wss://rinkeby.infura.io/ws/v3/
# for local test with ganache no need to set these.
# for local test against Infura create your own project and set these in .env.local or .env.production.local
# for CI and production set it as env var on CI/production server
# NB: Infura project secret is not supported yet (web3js auth?), use address whitelisting if necessary
# INFURA_PROJECT_ID =
# we consider a web3 connect attempt failed if no connected event received by this time (ms).
# Default set in code but you can override with this env var
# ETHEREUM_CONNECTION_TIMEOUT = 10000
# how often check if ethereum connection is still alive? (workaround for web3 not detecting websocket connection loss)
# Default set in code but you can override with this env var
# ETHEREUM_CONNECTION_CHECK_INTERVAL = 1000
# log ethereum tx success with LOG level after how many confirmation
LOG_AS_SUCCESS_AFTER_N_CONFIRMATION = 12
####################################################
######### MatchMaker settings
####################################################
# set acc and priv key on hosting provider
#MATCHMAKER_ETHEREUM_ACCOUNT =
#MATCHMAKER_ETHEREUM_PRIVATE_KEY =
# set to high (30 mins) not to keep sending match tx-s when mainnet is congested (multi match is only a convenience feature)
# TODO: check and test this param against transactionBlockTimeout web3 param once it's working in web3js... That should be increased in order to this param to work
MATCHMAKER_CHECKANDMATCHORDERS_TIMEOUT = 1800000
####################################################
######### ratesFeeder settings
####################################################
#RATESFEEDER_ETHEREUM_ACCOUNT = <set the account as env var>
# NEVER COMMIT PRIVATE KEYS of real accounts!!! NB: make sure you have a leading 0x
#RATESFEEDER_ETHEREUM_PRIVATE_KEY = <set the private key as env var>
# consider setRate ethereum tx failed after this time (in ms)
# ratesFeeder will try to send setRate again when next checkticker triggered. 5 mins for rinkeby/mainnet
# NB: If web3js transactionBlockTimeout: 50 (wss) or transactionPollingTimeout: 480 (http)
# is not reached for any reason. Normally web3 will timeout sooner, it is just an extra timeout to be 100% we schedule a next check.
# set to low (5mins) to send again sooner even when mainnet is congested (as setrate is crucial )
RATESFEEDER_SETRATE_TX_TIMEOUT = 300000
# how often compare ticker prices in state to decide if Augmint on chain price needs to be updated (in ms). Set to 0 to disable (for tests)
# NB: ticker prices in state and their update interval is based on their settings.
RATESFEEDER_CHECK_TICKER_PRICE_INTERVAL = 30000
# when to update Augmint rate? A rate update tx will be sent to chain if live ticker price (avg) is lower/higher by this % than current Augmint rate
# in % (i.e. 1 = 1%)
RATESFEEDER_LIVE_PRICE_THRESHOLD_PT = 2
####################################################
######### Ticker Providers settings
####################################################
# how often fetch new ticker info (in ms).
# there is a default value of 30000 (30secs) in code if it's not set
# you can also override for each provider individually: [COINBASE|KRAKEN|BITSTAMP]_HTTP_POLL_INTERVAL
HTTP_POLL_INTERVAL = 30000
# if fetch fails and next polling gets the same error we don't log again for this amount of time (minutes)
# there is a default 120 minutes in code if this is not set
LOG_POLL_ERROR_AGAIN_AFTER_X_MINS = 120
# after how many ms consider a http fetch as timed out
# there is a default of 30000 (30 secs) set in code if it's is not set
HTTP_FETCH_TIMEOUT = 30000
####################################################
######### Status API settings
####################################################
# heroku sets PORT env
#PORT = 80
# log level for morgan logger. see https://github.com/expressjs/morgan
# + additional "off" option: not use morgen at all (if production env provides http logging )
STATUSAPI_HTTP_LOG_LEVEL = off