Zander HillandMickael 56998116c3 fix (S3): incorrect ModifiedAt timestamps for S3 (#200 - #204) ...

The problem addressed here is that the FileInfo struct's FTime field is
set in S3 backend. This was being passed as milliseconds epoch. That
value was being passed into `time.Unix(x, 0)` which accepts arguments as
either/both (seconds, nanoseconds).

By passing milliseconds to this function expecting seconds, we have
wildly incorrect modified at timestamps.

I tested this against the same bucket that was problematic before and
it's now showing correctly :).

2019-09-29 21:56:14 +10:00

..

backend

fix (S3): incorrect ModifiedAt timestamps for S3 (#200 - #204)

2019-09-29 21:56:14 +10:00

formater

feature (search): content indexing: pdf, docx, txt, pptx, org

2019-04-04 19:34:24 +11:00

files.go

fix (path): default path when logging in - #151

2019-04-17 16:32:50 +10:00

index.go

feature (search): search feature

2019-04-02 19:48:50 +11:00

permissions.go

migrate (name): change project name

2019-01-28 01:09:45 +11:00

search.go

improve (config): listen for config changes for reactive configuration

2019-05-22 14:28:31 +10:00

share.go

improve (webdav): handle user restriction and password on the webdav server

2019-05-08 11:30:23 +10:00

webdav.go

improve (API): Cat now returns a io.ReadCloser to make it obvious it has to be closed

2019-04-04 19:27:06 +11:00