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 wonder what's up with the timestamps. According to #26 there should be timestamps in the logs, but I neither have timestamps in the .err's, nor the .log's. I'm using default configuration, backing up to a custom borg server (which works just fine btw, thanks a bunch!).
Also, while we're at timestamps, I wondered why you would use 220114 as a timestamp in the archive-names instead of 2022-01-14 or at least 2022014. It's an ISO-norm that makes a lot of sense imho. There are a lot of possible interpretations for e.g. 071211 ;)
Context
Hardware: VPS bought online
YunoHost version: 4.3.6
I have access to my server: Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
If yes, please explain: I use a custom borg-repository that I set up
Using, or trying to install package version/branch: 1.1.16~ynh28
Thank you so much for this app ❤️
The text was updated successfully, but these errors were encountered:
Describe the bug
I wonder what's up with the timestamps. According to #26 there should be timestamps in the logs, but I neither have timestamps in the .err's, nor the .log's. I'm using default configuration, backing up to a custom borg server (which works just fine btw, thanks a bunch!).
Also, while we're at timestamps, I wondered why you would use 220114 as a timestamp in the archive-names instead of 2022-01-14 or at least 2022014. It's an ISO-norm that makes a lot of sense imho. There are a lot of possible interpretations for e.g. 071211 ;)
Context
Thank you so much for this app ❤️
The text was updated successfully, but these errors were encountered: