Desktop client
The Qubix Drive desktop app mounts your Qubix content as a local disk. The disk
looks like ordinary folders and files, and every change you save is written
straight back to your Qubix server — the way Google Drive for desktop works. It
lets you edit in VS Code, vim, or any tool, and copy files in and out with cp,
mv or rsync.
What's on the disk
The mounted disk has three top-level folders:
websites/— one folder per site, with its real file tree (index.html,static/…, images). Saving a file uploads a new version and the site keeps its history, exactly as when you edit in the panel.scripts/— your automation scripts, one.jsfile each, containing the script code. The schedule, on/off state and description stay in the panel.drive/— your Drive folders and pages.
You see only what your account is allowed to see, and the server decides what you may change — the same access as in the panel.
1. Install the FUSE driver
The app presents itself as a disk through a system component called FUSE. Install the one for your system first:
- macOS — macFUSE
- Windows — WinFsp
- Linux — libfuse
Without it the app starts but can't mount, and tells you the driver is missing.
2. Download the app
Open the Downloads page in the panel and download Qubix Drive for your system.
The app is not notarized by Apple yet. If macOS blocks it on first launch, allow it in System Settings → Privacy & Security, then open it again.
3. Log in
Run the app with the login command, giving your panel address and your account
email. You'll be asked for your password.
For the address you can paste any link copied from your panel — only the address
part is used. The session is saved on your computer, so you log in once. Check it
any time with qubix-fs whoami.
4. Mount the disk
macOS and Linux — give the app a folder to mount into:
qubix-fs mount ~/QubixDrive
The disk appears as a volume named Qubix.
Windows — just run qubix-fs mount; the disk appears as Q:\.
Leave the command running — it keeps the disk connected. Press Ctrl-C, or run
qubix-fs unmount ~/QubixDrive, to disconnect.
Working with the disk
Open, edit and save files as you would on any disk — each save goes back to your server. A few things behave differently from a plain local disk:
- Scripts can't be deleted from the disk. So you don't remove a live automation by accident, deleting a script file is refused — remove scripts in the panel instead. Site files can be deleted (and their history is kept).
- You can only add the right kind of file in each folder. New scripts go under
scripts/as.jsfiles; new Drive pages go underdrive/. New sites, scripts or top-level items aren't created just by making a folder at the root. - Names may get a short suffix. When two items share a name, the app adds a
short code in brackets — for example
My landing [a1b2c3d4]— so each is distinct. The code is just for telling them apart. - There's no offline mode. The disk is a live view of your server. If the connection drops, saving fails until it's back — nothing is queued. A save that's rejected (for example a script with a syntax error) leaves the stored version untouched.
- Access is enforced by the server. If you don't have permission to change something, the save is refused — the same rules as in the panel.
If your session expires or is revoked, the disk can no longer reach the server and
the app tells you to reconnect. Run the login command again to restore it.