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
[0pcom@host skywire-deployment]$ dmsg-server start -c dmsg-config.json
Version "unknown" built on "unknown" against commit "unknown"
[2023-05-05T13:02:06.84158968-05:00] FATAL [dmsg_srv]: parsing config failed, generating default one... error="no config location specified"
[0pcom@host skywire-deployment]$ ls dmsg-config.json
dmsg-config.json
[0pcom@host skywire-deployment]$ dmsg-server start -c $(pwd)/dmsg-config.json
Version "unknown" built on "unknown" against commit "unknown"
[2023-05-05T13:02:35.47603325-05:00] FATAL [dmsg_srv]: parsing config failed, generating default one... error="no config
location specified"
$ dmsg-server start --help
Start Dmsg Server
Usage:
dmsg-server start [flags]
Flags:
-c, --config string location of config file (STDIN to read from standard input) (default "config.json")
-h, --help help for start
-m, --metrics string address to serve metrics API from
--stdin whether to read config via stdin
--syslog string address in which to dial to syslog server
--syslog-lvl string minimum log level to report (default "debug")
--syslog-net string network in which to dial to syslog server (default "udp")
--tag string tag used for logging and metrics (default "dmsg_srv")
it works to pipe the config to stdin
cat dmsg-config.json | dmsg-server start -c STDIN
The text was updated successfully, but these errors were encountered:
this was built from develop branch
![image](https://user-images.githubusercontent.com/36607567/236534244-cfe9717f-4460-4bb5-a653-f0bfcd9191c8.png)
it works to pipe the config to stdin
The text was updated successfully, but these errors were encountered: