forked from ymzkryo/chainpoint-node
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.sample
More file actions
106 lines (96 loc) · 3.42 KB
/
Copy path.env.sample
File metadata and controls
106 lines (96 loc) · 3.42 KB
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
105
106
#####################################################################
# Chainpoint Node Configuration
#####################################################################
# A valid Ethereum address that has been assigned the minimum
# balance of TNT tokens required to operate a Node.
#
# An address that does not meet the minumum balance is ineligible
# for TNT rewards for Nodes. A valid Ethereum address has
# 40 hex ([0-9a-fA-F]) characters preceded by `0x`.
#
# EXAMPLES:
#
# YES : 0x4205fC28a8Bb5E6199717cAFdE36507aB4F91EE4
#
# NO! : 4205fC28a8Bb5E6199717cAFdE36507aB4F91EE4
#
# NO! : 4205fC28
#
NODE_TNT_ADDRESS=
# A URI with an IPv4 Address [OPTIONAL]
#
# IMPORTANT : Don't forget the 'http://' prefix!
#
# Private IP Address Space IP Addresses:
#
# If you provide an IP address that is in the RFC1918 Private
# address space shown below, your Node will operate properly, but it
# will not be audited, as it will not be publicly available.
# It also won't be eligible for TNT rewards.
#
# 10.0.0.0 – 10.255.255.255
# 172.16.0.0 – 172.31.255.255
# 192.168.0.0 – 192.168.255.255
#
# The same applies for special addresses 0.0.0.0 and 127.0.0.1
#
# You can also leave this value empty if you don't want to advertise
# your Node publicly.
#
# EXAMPLES:
#
# YES : http://123.456.789.123 # Will be publicly advertised
#
# OK : http://10.0.1.2 # Will NOT be publicly advertised (RFC 1918 private address)
#
# NO! : http://mynode.example.com # DNS domain names are not allowed
#
# NO! : 123.456.789.123 # Missing URI scheme [http, https] are not allowed
#
CHAINPOINT_NODE_PUBLIC_URI=
# A URI with a Private (RFC1918) IPv4 Address [OPTIONAL]
#
# IMPORTANT : Don't forget the 'http://' prefix!
#
# Private IP Address Space IP Addresses:
#
# If you provide an IP address that is in the RFC1918 Private
# address space shown below, your Node will be able to provide additional metadata
# when calls to POST /hashes are made to your node. This is most beneficial when you've
# decided to host one-or-many Chainpoint Nodes behind a load balancer.
#
# 10.0.0.0 – 10.255.255.255
# 172.16.0.0 – 172.31.255.255
# 192.168.0.0 – 192.168.255.255
#
# EXAMPLE: http://10.0.0.1
CHAINPOINT_NODE_PRIVATE_URI=
# Include additional metadata in the response body of a hash submission [OPTIONAL]
#
# An enumerated data type consisting of two enumerals (public|private)
#
# When CHAINPOINT_NODE_REFLECTED_URI=public, the response body of a POST to /hashes will embed
# the value that has been set for CHAINPOINT_NODE_PUBLIC_URI in the 'meta' nested object of the resonse ('.meta.uri')
CHAINPOINT_NODE_REFLECTED_URI=
#####################################################################
# OPTIONAL SETTINGS
#####################################################################
# Node Web Console
# A web based Node dashboard is available at http://NODE_IP/
#
# By default, the password for this dashboard is set to the same
# value as the NODE_TNT_ADDRESS set above.
#
# Optionally you may specify a custom password to access it by
# uncommenting and setting the CHAINPOINT_NODE_UI_PASSWORD variable
# below to a password of your choice. Allows characters [a-zA-Z0-9]
#
# Alternatively, you can make your Node's dashboard available to the
# public, with no password required, by setting this value to 'false'
#
# EXAMPLES:
#
# CHAINPOINT_NODE_UI_PASSWORD=foobar
# CHAINPOINT_NODE_UI_PASSWORD=false
#
#CHAINPOINT_NODE_UI_PASSWORD=