Closed brokeh closed 6 months ago
Hey, thanks for the PR! I'll look into that, but currently, I see that as an added benefit for troubleshooting backup issues (last pushed entry in the log, modification time etc)
No worries. If there's utility in that behaviour then I can change it to be configurable via an env var then. Does that sound OK?
No worries. If there's utility in that behaviour then I can change it to be configurable via an env var then. Does that sound OK?
We ask people to provide this logfile to see why there may be an issue with the app not starting/installing, etc and therefore we need a defined path to the logfile and that path should not change. I think it's best to add the file to the exception list in Backblaze so that it's not backed up. I put it in the root of C: intentionally that it's not dependent on any wine installation or initialization.
I have no issues with myself (and presumably most others who explicitly set an environment variable) opening a shell into the Docker container and grabbing the log files out from the backend if necessary.
As for excluding it in the Backblaze config, as far as I can tell this is not possible under the current setup. It is only possible to exclude folders and file extensions. Since this is put straight into the root of C:\ it is not possible to exclude it by folder and I do want *.log
files as there are some log files in other locations I do want backed up.
Not sure why the CI is filing on this. Doesn't seem like anything related to the change
Not sure why the CI is filing on this. Doesn't seem like anything related to the change
yes, that's ecxpected.
So that it is not included in the pushed backups