-
Notifications
You must be signed in to change notification settings - Fork 129
Expand file tree
/
Copy path.env
More file actions
93 lines (73 loc) · 3.26 KB
/
Copy path.env
File metadata and controls
93 lines (73 loc) · 3.26 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
# tyd1 = Talkyard, development, epoch 1. [7RJPW2]
COMPOSE_PROJECT_NAME=tyd1
# The registry and organization to which Docker images you build should be pushed.
DOCKER_REG_ORG=debiki
# ----- Networks [TYINTNET]
# Give containers static ips, because things in the OS or applications seem to
# remember the containers ip addresses (even if Docker's DNS server return
# up-to-date ips) and requests then can fail to reach their destination,
# if a container gets restarted with a new dynamic ip.
#
# Update 2025: Gemini says we can use his: [docker_dyn_ips]
# -Dsun.net.inetaddr.ttl=60
# to make the JVM remember ip addrs for 60 seconds only. But it's not only
# the JVM that caches ip addrs. Turns out that also HikariCP might remember
# ip addrs, so might need to config e.g. `db.default.hikaricp.maxLifetime`.
# And add `resolver 127.0.0.11 valid=30s` to Nginx. — Let's just keep
# using ip addrs, has been working fine.
#
# Use 172.27.{1,2,3,4,5}. 127.26 is used in prod, and 172.27.0 is used in the
# Talkyard v0 dev env, but 172.27.{1,2,3,4,5} are not used in v0. (Reusing a subnet
# could cause ip addr space collision problems when switching between
# prod and dev environments on localost, or between v0 and v1.)
FE_PUB_NET_SUBNET=172.27.1.0/24
FE_INT_NET_SUBNET=172.27.2.0/24
BE_INT_NET_SUBNET=172.27.3.0/24
EG_INT_NET_SUBNET=172.27.4.0/24
EG_PUB_NET_SUBNET=172.27.5.0/24
TEST_INT_NET_SUBNET=172.27.8.0/24
TEST_PUB_NET_SUBNET=172.27.9.0/24
# An external network, not part of the Talkyard installation at all.
# E.g. for pretending there's an external website somewhere, with a SSO page,
# or blog posts that embed Talkyard blog comments.
# This is a bogon ip addr range, reserved for e.g. testing, but no real websites on
# Planet Earth have an addr in this range.
# Smokescreen allows traffic to here (but not to 172.27.9.0/24, which I first tried
# to use).
TEST_EXT_NET_SUBNET=203.0.113.0/24
# 1..19 is for Docker's gateway, and for Docker's DHCP server to use if needed.
# Docker's DHCP server seems to pick as low ip addresses as possible — so don't
# use 172.28.0. 2, 3, 4, 5 etc ourselves for static ips (because the containers
# would then fail to start, if Docker has used the ip for sth else, like
# a temporary test container we've started, already). Start at 21 instead.
# 21..29 for Nginx web servers.
FE_PUB_NET_WEB_IP=172.27.1.21
FE_INT_NET_WEB_IP=172.27.2.21
# 31..39 for Redis cache servers.
FE_INT_NET_CACHE_IP=172.27.2.31
# 41..49 for app servers.
FE_PUB_NET_APP_IP=172.27.1.41
FE_INT_NET_APP_IP=172.27.2.41
BE_INT_NET_APP_IP=172.27.3.41
EG_INT_NET_APP_IP=172.27.4.41
TEST_INT_NET_APP_IP=172.27.8.41
# 51..59 for Deno renderer servers.
BE_INT_NET_RENDR_IP=172.27.3.51
# 61..69 for database (PostgreSQL).
BE_INT_NET_RDB_IP=172.27.3.61
BE_INT_NET_RDB2_IP=172.27.3.62
# 71..79 for an ElasticSearch cluster.
FE_PUB_NET_SEARCH_IP=172.27.1.71
BE_INT_NET_SEARCH_IP=172.27.3.71
# 81..89 for logging, analytics, tracing.
BE_INT_NET_TRACER_IP=172.27.3.81
# 99 is the egress proxy.
EG_INT_NET_EGRESSP_IP=172.27.4.99
EG_PUB_NET_EGRESSP_IP=172.27.5.99
# So can talk to fakeweb.
TEST_EXT_NET_EGRESSP_IP=203.0.113.99
# 111..127 for test containers.
TEST_INT_NET_FAKEMAIL_IP=172.27.8.112
TEST_PUB_NET_FAKEMAIL_IP=172.27.9.112
TEST_EXT_NET_FAKEWEB_IP=203.0.113.119
TEST_EXT_NET_GHOST_IP=203.0.113.120