You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Backend location, the nginx config currently hardcodes it to http://service:8383
Enketo location, the nginx and backend configs currently hardcode it to http://enketo:8005 and http://enketo:8005/-; the Enketo config currently hardcodes a subpath of -. I believe Central itself knows about and uses the - suffix.
Pyxform location, the service config currently hardcodes it to a host of pyxform and a port of 80
Enketo redis dbs, the Enketo config currently hardcodes the main db to enketo_redis_main with port of 6379 and the cache db to enketo_redis_cache with port of 6380. If we were to make this one configurable from .env, we should set the url for each db which is more flexible than setting host and port (see docs).
Currently uses who want this level of configurability need to use their own way of editing the relevant config files.
So far, we've kept configurability to a minimum and treated the Docker Compose file as the preferred way of running. A the same time, we know some users prefer to orchestrate services themselves.
From @matthew-white: these get configured differently for local dev as well (e.g. 127.0.0.1) so there's a benefit for that context as well.
From my perspective, adding these variables makes all the service interdependencies configurable (and therefore the pre-built images generally more usable), without adding materially to the size of docker-compose.yml (9 lines added to a 151 line file).
As proposed by @tobiasmcnulty at #546
This would mean adding env vars for:
http://service:8383
http://enketo:8005
andhttp://enketo:8005/-
; the Enketo config currently hardcodes a subpath of-
. I believe Central itself knows about and uses the-
suffix.pyxform
and a port of80
enketo_redis_main
with port of6379
and the cache db toenketo_redis_cache
with port of6380
. If we were to make this one configurable from .env, we should set theurl
for each db which is more flexible than setting host and port (see docs).Currently uses who want this level of configurability need to use their own way of editing the relevant config files.
So far, we've kept configurability to a minimum and treated the Docker Compose file as the preferred way of running. A the same time, we know some users prefer to orchestrate services themselves.
From @matthew-white: these get configured differently for local dev as well (e.g. 127.0.0.1) so there's a benefit for that context as well.
CC @spwoodcock
The text was updated successfully, but these errors were encountered: