fix: integration tests for windows

.github/workflows/windows.yml

@@ -1,23 +1,25 @@
-name: windows
-
-on: [push, pull_request]
-
-env:
-  CARGO_TERM_COLOR: always
-
-jobs:
-  build:
-    runs-on: windows-2019
-
-    steps:
-      - uses: actions/checkout@v2
-      - name: Build
-        run: cargo build --all-features
-      - name: Format
-        run: cargo fmt --all -- --check
-      - name: Clippy
-        run: cargo clippy -- -Dwarnings
-      - name: Run tests
-        run: cargo test --no-fail-fast
-        env:
-          RUST_LOG: trace
+name: windows
+
+on: [push, pull_request]
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  build:
+    runs-on: windows-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: install dokany
+        run: choco install dokany
+      - name: Build
+        run: cargo build --all-features
+      - name: Format
+        run: cargo fmt --all -- --check
+      - name: Clippy
+        run: cargo clippy -- -Dwarnings
+      - name: Run tests
+        run: cargo test --no-fail-fast --features integration-tests
+        env:
+          RUST_LOG: trace

README.md

@@ -6,7 +6,7 @@
 
 <p align="center">~ A FUSE Driver for remotefs-rs ~</p>
 
-<p align="center">Developed by <a href="https://veeso.github.io/" target="_blank">@veeso</a></p>
+<p align="center">Developed by <a href="https://veeso.me/" target="_blank">@veeso</a></p>
 <p align="center">Current version: 0.1.0</p>
 
 <p align="center">
@@ -162,6 +162,8 @@ All the features are enabled by default; so if you want to build it with only ce
 remotefs-fuse-cli -o opt1 -o opt2=abc --to /mnt/to --volume <volume-name> <aws-s3|ftp|kube|smb|scp|sftp|webdav> [protocol-options...]
 ```
 
+On Windows the mountpoint can be specified simply using the drive letter `--to M` will mount the FS to `M:\`
+
 where protocol options are
 
 - aws-s3
@@ -210,6 +212,8 @@ Mount options can be viewed in the docs at <https://docs.rs/remotefs-fuse/latest
 
 ## UID and GID override
 
+> ❗ This doesn't apply to Windows.
+
 The possibility to override UID and GID is used because sometimes this scenario can happen:
 
 1. my UID is `1000`
@@ -221,7 +225,11 @@ That's why I've added `Uid` and `Gid` into the `MountOption` variant.
 
 Setting the `Uid` option to `1002` you'll be able to operate on the File system as it should.
 
-> ❗ This doesn't apply to Windows.
+## Project stability
+
+Please consider this is an early-stage project and I haven't heavily tested it, in particular the Windows version.
+
+I suggest you to first test it on test filesystems to see whether the library behaves correctly with your system.
 
 ## Changelog ⏳
 

remotefs-fuse-cli/src/main.rs

@@ -44,6 +44,7 @@ fn main() -> anyhow::Result<()> {
     log::info!("Mounting remote fs at {}", mount_path.display());
 
     // create the mount point if it does not exist
+    #[cfg(unix)]
     if !mount_path.exists() {
         log::info!("creating mount point at {}", mount_path.display());
         std::fs::create_dir_all(&mount_path)?;

remotefs-fuse/Cargo.toml

@@ -33,13 +33,15 @@ nix = { version = "0.29", features = ["fs"] }
 dashmap = "6"
 dokan = "0.3.1"
 dokan-sys = "0.3.1"
+path-slash = "0.2"
 widestring = "0.4.3"
 winapi = "0.3.9"
 
 [dev-dependencies]
 env_logger = "^0.11"
 pretty_assertions = "^1"
 remotefs-memory = "0.1"
+serial_test = "^3"
 
 [target.'cfg(unix)'.dev-dependencies]
 nix = { version = "0.29", features = ["user"] }