[Docker] How does docker transform EBUSD_*
to ebusd arguments?
#614
Commifreak
started this conversation in
General
Replies: 3 comments 1 reply
-
this is not related to docker at all. it is ebusd interpreting the env vars. docs are here and here |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yep, I found that already but not the code for handling those variables :/
Gruß,
R. Kluth
… Am 28.06.2022 um 07:27 schrieb John ***@***.***>:
this is not related to docker at all. it is ebusd interpreting the env vars. docs are here and here
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
I even searched for „EBUSD_“ but did not found that spot. Weird.
Thanks!
Gruß,
R. Kluth
… Am 02.07.2022 um 09:08 schrieb John ***@***.***>:
not difficult to find when looking for "env": main.cpp:1315-1354
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I noticed, that ebusd docker image can be controlled via env's. But I did not found out: how? I just seen the usage of predefined envs inside the app running inside the container, but somehow all
EBUSD_
starting env's are converted to a--
argument? How is that working? Docker magic?And how does docker know
EBUSD_
has to be cut?Beta Was this translation helpful? Give feedback.
All reactions