Method 3: Install script, offline
Use this when the server can’t download from GitHub (no internet, or GitHub is filtered).
Step 1: Download the package on another computer, from Releases:
flock-server-linux-x64.tar.gz(most servers) orflock-server-linux-arm64.tar.gz(ARM servers; check withuname -m)- the matching
.sha256file (optional, to verify the download)
Step 2: Copy them to the server, for example:
scp flock-server-linux-x64.tar.gz* user@your-server:~Step 3: Unpack and verify
sha256sum -c flock-server-linux-x64.tar.gz.sha256 # should print "OK"tar -xzf flock-server-linux-x64.tar.gzStep 4: Make sure PostgreSQL is available. The package contains everything except the database. Either:
- let the installer install PostgreSQL. This needs the OS package sources (
apt/dnf), which often work even when GitHub doesn’t, or - install it yourself from local media or a mirror (
sudo apt install postgresql/sudo dnf install postgresql-server), or - use an existing database with
--db-url postgres://user:pass@host:5432/flockin the next step.
Step 5: Install
sudo ./flock-server/install.sh --domain chat.example.comIt accepts the same options as method 2. --domain needs the server to reach Let’s Encrypt; without it, Flock answers on http://<server-ip>:4000.
Updating: download the new package the same way and run its install.sh (or sudo flockctl update --package /path/to/package.tar.gz). Configuration and database are kept. flockctl works as in method 2.
For a fully manual installation (no script), see deploy/INSTALL.md.
