First tagged build of Discord Drive: an SFTP server whose storage backend is
Discord.
Read the warning at the top of the README
before you install this. Storing general files on Discord is a grey area, and
the risk lands on your account rather than on this project. Do not make it the
only copy of anything.
Which download
| Asset | What it is |
|---|---|
DiscordDrive-0.1.0-setup.exe |
The desktop app, as an installer. Start here if you are not sure. |
DiscordDrive-0.1.0-portable.exe |
The same app, nothing installed. |
discord-drive.exe |
The standalone backend on its own: a console program, no Docker and no Electron. The desktop app already bundles a copy of this. |
Windows x64 only. PyInstaller and electron-builder each build for the
platform they run on, so macOS and Linux need a build from source — see
CONTRIBUTING.md.
The standard (Docker) build is not a download. Clone the repository and run
.\scripts\start.ps1. The README explains which of the two to pick; they are
two products, and there is no migration in either direction.
It will not start until Discord is set up
You need a bot token, a DM or a channel for the chunks to live in, and a
password of at least 12 bytes. Step 1 of the README walks through all of it.
That password is not just a login — it wraps the key every stored file is
encrypted with. Losing it loses the files. There is no recovery path.
These binaries are unsigned
There is no code-signing certificate, so Windows SmartScreen will warn about
all three. Check what you downloaded against these:
Get-FileHash .\DiscordDrive-0.1.0-setup.exe -Algorithm SHA256| Asset | SHA-256 |
|---|---|
discord-drive.exe |
0a9e1e69d202072a52b80916aece2768ecd5222457a8aa36fb94f05244ab4168 |
DiscordDrive-0.1.0-portable.exe |
b99de20b48bcfd091ca117c0360c6ebbfd486e315fea59d022aa682185df4645 |
DiscordDrive-0.1.0-setup.exe |
8534e8db4db57b4e4cb045b949d447a540e59726028b4eca618a959be6b1f542 |
Status
Single user, single replica, in real use against a real bot token. Verified at
this commit: 764 passed under pytest, 761 passed and 3 skipped against a real
SQLite backend, and 16 node --test — including the block that drives the
packaged discord-drive.exe rather than a stub.
The known gaps are written down rather than glossed over:
docs/OPERATIONS.md.