Mount cloud storage as a local filesystem using FUSE.

Supported providers: TeraBox · Dropbox · Box · pCloud · Google Drive · JSON FS (local test filesystem)

Features:

• Read-only or read-write (create / delete / move)
• Block-level data cache with prefetch
• Configurable cache pool size and concurrency
• Linux and macOS (Intel and Apple Silicon)

npm install -g unidisk

After installation the unidisk command is available system-wide.

npx unidisk [options] <mountPoint>

git clone https://github.com/weilonge/unidisk
cd unidisk
npm install
npx tsx src/udFuse.ts [options] <mountPoint>

1. Install macFUSE (download the .pkg from the releases page).
2. Install pkg-config:

   brew install pkg-config
   

1. Install macFUSE.
2. Install Xcode Command Line Tools if not already present:

   xcode-select --install
   

3. Rebuild the native addon:

   npm rebuild fuse-native
   

sudo apt install libfuse2

fuse-native bundles an x86_64 libfuse that the arm64 linker rejects. Use the following sequence instead of a plain npm install:

1. Install the FUSE library and build tools:

   sudo apt install libfuse2 libfuse-dev build-essential
   

2. Install JS dependencies without running native build scripts:

   npm install --ignore-scripts
   

3. Patch the bundled library and rebuild the native addon:

   npm run setup:rpi
   

   This copies the system arm64 libfuse into place and runs npm rebuild fuse-native.

Copy the sample settings file and customize cache_path:

mkdir -p ~/.unidisk
cp node_modules/unidisk/dist/settings.json.SAMPLE ~/.unidisk/settings.json

When running from source use dist/settings.json.SAMPLE directly.

~/.unidisk/settings.json controls global tunables (block size, cache size, concurrency) and named profiles. The full set of keys with their defaults:

{
  "block_reading_size":  1048576,
  "block_writing_size":  8388608,
  "fuse_iosize":         65536,
  "queue_concurrency":   1,
  "prefetch_blocks":     3,
  "max_data_cache_entry": 25,
  "cache_path":          "/tmp/ud/cache",
  "profile": {}
}

Global settings can also be placed directly in the profile JSON file instead of (or alongside) ~/.unidisk/settings.json. When -p /path/to/profile.json is used, unidisk reads settings from that file, so a single self-contained profile file is enough:

{
  "module":              "Dropbox",
  "token":               "<accessToken>",
  "cacheStore":          "disk",
  "cachePath":           "/tmp/dropbox-cache",
  "block_reading_size":  4194304,
  "queue_concurrency":   2,
  "prefetch_blocks":     3
}

unidisk [options] <mountPoint>

Options:
  -m <module>   Provider name: Sample | Dropbox | TeraBox
                Optional when the profile JSON already has a "module" field.
  -p <profile>  Path to a profile JSON file, or a named profile from
                ~/.unidisk/settings.json
  -w            Enable write support (create / delete / move)
  -v            Verbose logging
  -d            FUSE debug output

1. Log in at terabox.com, open DevTools → Application → Cookies, and copy the ndus cookie value. Or run this in the browser console:

   document.cookie.split('; ').find(c => c.startsWith('ndus='))?.split('=')[1]

2. Create a profile file, e.g. ~/.unidisk/terabox.json:

   {
     "module": "TeraBox",
     "cacheStore": "disk",
     "cachePath": "/tmp/terabox-cache",
     "ndus": "<paste ndus value here>"
   }

3. Mount:

   mkdir -p ~/mnt/terabox
   unidisk -p ~/.unidisk/terabox.json ~/mnt/terabox
   

4. Unmount:

   fusermount -u ~/mnt/terabox        # Linux
   umount ~/mnt/terabox               # macOS
   

Tip (Raspberry Pi / slow connections): set "queue_concurrency": 1 in the profile to avoid CDN throttle errors.

1. Go to the Box Developer Console, create an app (Custom App → User Authentication OAuth 2.0), then under Configuration → Developer Token click Generate Developer Token.

2. Create a profile, e.g. ~/.unidisk/box.json:

   {
     "module": "Box",
     "cacheStore": "disk",
     "cachePath": "/tmp/box-cache",
     "token": "<developer token>"
   }

3. Mount:

   mkdir -p ~/mnt/box
   unidisk -p ~/.unidisk/box.json ~/mnt/box
   

4. Unmount:

   fusermount -u ~/mnt/box        # Linux
   umount ~/mnt/box               # macOS
   

Note: Developer tokens expire after 60 minutes. For long-running mounts use a proper OAuth 2.0 refresh-token flow and supply a long-lived access token.

Upload limit: The simple upload path supports files up to ~50 MB. Larger files require Box's chunked upload API (not yet implemented).

1. Go to the pCloud App Console, create an app, then use the OAuth 2.0 authorization flow to obtain a long-lived access token. For quick testing you can also use the pCloud API Explorer which lets you call userinfo?getauth=1 with your credentials to get a token.

2. Create a profile, e.g. ~/.unidisk/pcloud.json:

   {
     "module": "pCloud",
     "cacheStore": "disk",
     "cachePath": "/tmp/pcloud-cache",
     "token": "<access token>"
   }

   EU-region accounts must add "apiHost": "eapi.pcloud.com" (default is api.pcloud.com for US accounts).

3. Mount:

   mkdir -p ~/mnt/pcloud
   unidisk -p ~/.unidisk/pcloud.json ~/mnt/pcloud
   

4. Unmount:

   fusermount -u ~/mnt/pcloud        # Linux
   umount ~/mnt/pcloud               # macOS
   

1. Go to the Google OAuth 2.0 Playground:

   • In the left panel under Drive API v3, tick https://www.googleapis.com/auth/drive.
   • Click Authorize APIs, sign in, then Exchange authorization code for tokens.
   • Copy the Access token (valid for 1 hour).

   For a long-lived token, create a project in the Google Cloud Console, enable the Google Drive API, configure OAuth 2.0 credentials, and implement a refresh-token flow.

2. Create a profile, e.g. ~/.unidisk/gdrive.json:

   {
     "module": "GoogleDrive",
     "cacheStore": "disk",
     "cachePath": "/tmp/gdrive-cache",
     "token": "<access token>"
   }

3. Mount:

   mkdir -p ~/mnt/gdrive
   unidisk -p ~/.unidisk/gdrive.json ~/mnt/gdrive
   

4. Unmount:

   fusermount -u ~/mnt/gdrive        # Linux
   umount ~/mnt/gdrive               # macOS
   

Note: Google Workspace documents (Docs, Sheets, Slides, etc.) are excluded from directory listings because they have no downloadable binary content via the Drive files API.

1. Prepare a JSON file or use examples/sample-fs.json.

2. Create a profile, e.g. ~/.unidisk/sample.json:

   {
     "module": "Sample",
     "cacheStore": "memory",
     "JSONPath": "/path/to/sample-fs.json"
   }

3. Mount:

   mkdir -p /tmp/mnt
   unidisk -p ~/.unidisk/sample.json /tmp/mnt
   

4. Unmount:

   fusermount -u /tmp/mnt             # Linux
   umount /tmp/mnt                    # macOS
   

1. Obtain an access token from the Dropbox developer console.

2. Create a profile, e.g. ~/.unidisk/dropbox.json:

   {
     "module": "Dropbox",
     "cacheStore": "disk",
     "cachePath": "/tmp/dropbox-cache",
     "token": "<accessToken>"
   }

3. Mount:

   mkdir -p ~/mnt/dropbox
   unidisk -p ~/.unidisk/dropbox.json ~/mnt/dropbox
   

4. Unmount:

   fusermount -u ~/mnt/dropbox        # Linux
   umount ~/mnt/dropbox               # macOS
   

Instead of passing a JSON file path every time, add a named profile to ~/.unidisk/settings.json:

{
  "profile": {
    "MyTeraBox": {
      "module": "TeraBox",
      "cacheStore": "disk",
      "cachePath": "/tmp/terabox-cache",
      "ndus": "<ndus value>"
    },
    "MySample": {
      "module": "Sample",
      "cacheStore": "memory",
      "JSONPath": "/home/user/sample-fs.json"
    }
  }
}

Then mount by profile name:

unidisk -p MyTeraBox ~/mnt/terabox
unidisk -p MySample  /tmp/mnt

• FUSE: Filesystem in Userspace
• fuse-native
• macFUSE