4 ms·
It's not always just "foreign" filesystems where it happens. I hooked up my MBPro to my two Linux machines with Syncthing, and suddenly I had .DS_Store files i
by pixelesque 2y ago
It's not always just "foreign" filesystems where it happens.
I hooked up my MBPro to my two Linux machines with Syncthing, and suddenly I had .DS_Store files in all my shares directories on both of those Linux machines.
I then had to set up .stignore files to ignore the further syncing of them and also had to iradicate the files manually.
My Syncthing shares were in my $HOME/Sync/ directory on my MBPro (M2), which should be the main drive mount as far as I'm aware?
- pixelesque 2y agoAlso: the way I discovered this was that one of the directories was the shared directory for my website blog (both source and target static-site generated files), and from my Linux machine I had r-synced that to my remote web server, and noticed bots had found these .DS_Store files in most directories of my website, which included (due to the .DS_Store files) unlinked files which the crawlers wouldn't have found if not for the .DS_Store files. So I was then getting 200 HTTP requests on the .DS_Store files and I noticed that in my server logs, and then it occurred to me how they had got there (via Syncthing, and me not noticing them locally on the Linux machines until I looked for them and found them).
- Joel_Mckay 2y agoDid you try a filter like rsync's --exclude=".*/" Or an Apache regex config like: <FilesMatch "^\."> Order allow,deny Deny from all </FilesMatch> Or something like: RewriteRule ^(.*/)?\.git+ - [R=404,L] RedirectMatch 404 ^(.*/)?\.git+ Good luck =3