SilverBullet is distributed as a single server binary available for the following platforms:
note Which file should I download? The releases page lists two families of zip files:
silverbullet-server-<os>-<arch>.zip: this is what you want, the actual SilverBullet server.sb-<os>-<arch>.zip— the optional Integrations/CLI tool (sb) for scripting against a running server.
We start by downloading the silverbullet-server-* zip for your platform from GitHub.
Unzip this archive somewhere convenient. You’ll get a single silverbullet executable.
Then, create a folder to hold your data (your server configuration and space files will live here):
mkdir data
Run the server, pointing it at that folder:
./silverbullet data
Since data is empty, this opens a first-run setup wizard for accounts and your first space — see Dashboard.
The server listens on http://localhost:3000 by default. To pick a different port, use -p:
./silverbullet -p 3001 data
And to bind on an address other than 127.0.0.1 (e.g. to make it reachable on your LAN), use -L:
./silverbullet -L 0.0.0.0 data
Now, open http://localhost:3000 in your browser and you’ll be guided through the initial Dashboard, once that’s all done, head to Getting Started to learn the basics.
To serve a folder of pages as a public, read-only website instead, without accounts or a data folder:
./silverbullet publish ./docs
publish listens on all interfaces (0.0.0.0) by default, since the site is public; -L and -p work here too. See Publishing#Publish a folder as a website.
You can upgrade your SilverBullet install based on the version you’d like to run.
To upgrade to the latest stable release:
./silverbullet upgrade
To upgrade to the latest edge release (which keeps in sync with the main development branch):
./silverbullet upgrade-edge
To upgrade your client, be sure to refresh your page twice somewhat slowly.
To check which version of SilverBullet you’re running, run the ${widgets.commandButton("Client: Version")} command.