My experience has been that remote use of VS Code over SSH is completely seamless. I never had to install any packages or do anything to manage VS Code state on the server side. It handles everything itself.
gwillen
joined 1 year ago
Personally, if correctly configured (and with a strong password), I treat this setup as more secure than anything more complex that I could assemble for myself.
It's very easy to accidentally screw up the configuration. Nginx is generally reverse-proxying some other server; if that server is exposed in any other way than via Nginx, your security is gone.
If you ever transmit the password over http (rather than https) by accident, your security is gone.
If you are somehow treating the three accounts as separate within the underlying application, I wouldn't trust the security of that part; I only use nginx with htpasswd to gate security of single-user apps.
If you're just serving static files, it's harder to mess up and most of these comments don't apply.
There are various reasons this could happen. For a small difference I wouldn't worry about it. Who knows how windows is even computing that number?
Given how small the difference is, I suspect some kind of difference in how Windows is allocating space for the files. Even though you say elsewhere that all the block size info you can find is the same, filesystems have gotten very complicated, and there could be other parameters you don't see.
Another possibility would be something like sparse files, if a file has empty space on the old drive that's been turned into zeroes taking up space on the new drive. I would hope the copy tool would handle that correctly but who knows.
It could be that some parameter inside Windows itself has changed in the meantime. For example, how much space it preallocates for storing filenames in an empty folder.