-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timezone in container #96
Comments
I have some bad news -- the log output from copyparty is not affected by TZ and is always UTC :-) if we want this feature, it would be a new option to the program arguments, so it wouldn't be docker specific. But this sounds like a good idea and I'll take a look. But just in case I've misunderstood you, could you include an example line from the log, just so we're sure we're talking about the same timestamp? |
fresh logs, coming right up:
|
yup, that's what i hoped you meant. I'll see if I can add an option to change the timezone; the reason I don't want to do that based on TZ is because that has many surprising side-effects into shared libraries. Thanks for the idea :> |
talked to some friends, turns out I was being a bit too paranoid about TZ... so the next version will use TZ for logs by default :-) and all docker image flavors except for the old behavior of forcing UTC can be restored by specifying I think the next release will be this weekend; need to fix something else first, and that's gonna require writing a lot of tests, so we'll see... thx again for the idea 😁 |
that's great! thanks a lot |
hello!
would it be possible to include alpine package
tzdata
in theDockerfile
?This way one could set environment variable
TZ
to the desired timezone and have logs with correct timestamp.thx~
The text was updated successfully, but these errors were encountered: