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
Hello.
I have a configuration file looking like this:
<runner>
daemon on
program easymonitor
socket-name _zdaemon.sock
transcript myapp.log
</runner>
I would like "socket-name" and "transcript" paths to be relative compared to where the configuration file lives.
As zdaemon is right now, in case a relative path is specified, os.getcwd() is assumed.
That means that I'm forced to specify an absolute path which of course is valid on my machine but may change somewhere else (production, staging. etc.).
I think there should a way to override this behavior, either by providing some kind of templating systems (e.g. "transcript {{HERE}}/myapp.log") or by assuming os.path.abspath(os.path.dirname(file)) in case of a relative path.
Thoughts?
The text was updated successfully, but these errors were encountered:
zdaemon uses ZConfig to read and interpret the config file. I think this bug should be reassigned to ZConfig. Something similar to zopefoundation/ZConfig#2 perhaps, with ${CONFFILEPATH} or better syntax?
Hello.
I have a configuration file looking like this:
I would like "socket-name" and "transcript" paths to be relative compared to where the configuration file lives.
As zdaemon is right now, in case a relative path is specified, os.getcwd() is assumed.
That means that I'm forced to specify an absolute path which of course is valid on my machine but may change somewhere else (production, staging. etc.).
I think there should a way to override this behavior, either by providing some kind of templating systems (e.g. "transcript {{HERE}}/myapp.log") or by assuming os.path.abspath(os.path.dirname(file)) in case of a relative path.
Thoughts?
The text was updated successfully, but these errors were encountered: