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
I am not sure why nobody has this reported yet. Maybe I'm just making a very stupid mistake, but when I try to pass the cli arg --config the config file is not read. I had a quick look into the code but I do not have any knowledge about the viper library that does the cli arg stuff.
Here is what I quicky tested in the cmd/main.go from line 43 on.
I ran it with the argument --config /home/usr/conf.yaml.
My output was:
___
+++ /home/usr/conf.yaml
So it seems that dagu does not read the --config arg somehow. I also tried the latest version 1.16.1 and nothing happens when you try to pass the --config argument.
I tried dagu start-all --config /home/usr/config.yaml but dagu just does not seem to care.
The text was updated successfully, but these errors were encountered:
I am not sure why nobody has this reported yet. Maybe I'm just making a very stupid mistake, but when I try to pass the cli arg
--config
the config file is not read. I had a quick look into the code but I do not have any knowledge about the viper library that does the cli arg stuff.cmd/main.go
from line 43 on.--config /home/usr/conf.yaml
.So it seems that dagu does not read the
--config
arg somehow. I also tried the latest version1.16.1
and nothing happens when you try to pass the--config
argument.I tried
dagu start-all --config /home/usr/config.yaml
but dagu just does not seem to care.The text was updated successfully, but these errors were encountered: