Skip to content
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

Strange date for directories #299

Open
jpds opened this issue Feb 26, 2024 · 3 comments
Open

Strange date for directories #299

jpds opened this issue Feb 26, 2024 · 3 comments

Comments

@jpds
Copy link

jpds commented Feb 26, 2024

I noticed that a strange last-modified date is displayed for directories when this module is used with a Garage cluster (files are fine):

Screenshot from 2024-02-26 23-39-38

Perhaps instead a - could be displayed for this case?

@jpds
Copy link
Author

jpds commented Feb 27, 2024

Hmm, having taken a look at the codebases - this needs to be fixed here: https://github.com/caddyserver/caddy/blob/03f703a00e006a1e53a2eaf5f4e33a1b3a5e4237/modules/caddyhttp/fileserver/browse.html#L976-L991

I do not however have an alternative S3 implementation to double check if a modified date is returned on AWS for directories before submitting a PR to fix this.

@ta2013
Copy link

ta2013 commented Jul 6, 2024

@jpds cloud you share part of s3 fs config in caddyfile ?

Thanks

@gedw99
Copy link

gedw99 commented Feb 1, 2025

Hey @jpds

I have tried Garage too . It’s not using Raft.

I ended up using NATS with each server running in leaf node archetype.

For minio can fire nats events, and so you get global sync.

For local fs, nats can do the same with a tiny bit of FS watching .

You still need a nats cluster somewhere so that the changes get synced between all your servers of course .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants