Ferry 1.0.3

Ferry 1.0.3 is a small update to the Ferry Web app. Your messages, files, devices and password are not touched.

Which file do I need?

• New install: download ferry-1.0.3-docker-compose.tar.gz. It is not the program itself but the three files Docker Compose needs: compose.yaml, .env.example and the backup script. Compose then pulls the program, the public image ghcr.io/max1874/ferry:1.0.3, for linux/amd64 or linux/arm64.
• Already running 1.0.0, 1.0.1 or 1.0.2? You do not need the download; see Upgrade.
• Source code (zip / tar.gz) is added by GitHub for developers. You do not need it to run Ferry.

What's changed

• Loading images look like they are loading. While an image was still on its way, the Web app showed the browser's broken-image icon and the file name, so it looked like the image had failed. It now shows a spinner until the image appears.
• Images no longer stay stuck loading. If the connection dropped or reconnected while an image was loading, the image could stay a grey box until the page was reloaded. It now loads again by itself once the connection is back. If the Server gives no answer for 60 seconds, the image turns into a file card you can tap to download.

Install

curl -fLO https://github.com/max1874/ferry/releases/download/v1.0.3/ferry-1.0.3-docker-compose.tar.gz
tar -xzf ferry-1.0.3-docker-compose.tar.gz
cd ferry
cp .env.example .env    # set FERRY_HOST_IP to this server's LAN IP
docker compose up -d
docker compose logs ferry

The README covers every step, other deployment paths and troubleshooting.

Upgrade

In your ferry directory, back up first:

scripts/ferry-data.sh backup ../ferry-backup-before-1.0.3.tar.gz

Change FERRY_IMAGE in .env to ghcr.io/max1874/ferry:1.0.3, then:

docker compose pull
docker compose up -d
docker compose logs --tail=100 ferry

Limits

• Ferry serves plain HTTP for a trusted private network. Keep it off the public Internet; a TLS reverse proxy of your own inside the private network is supported.
• Chrome and other Chromium browsers block downloads from a plain http:// address. Keep the file from the browser's download list, or allow "Insecure content" in the site settings for your Ferry address.

简体中文：https://github.com/max1874/ferry/blob/v1.0.3/docs/releases/1.0.3.zh-Hans.md

_{Image digest sha256:881e9273d6ffa3b9d34b8f66b00b39e85fbd0614c574d18d3138a05054def09f · commit 871b592 · CI run}

Ferry 1.0.2

Ferry 1.0.2 is a small update to the Ferry Server and Web app. Your messages, files, devices and password are not touched.

Which file do I need?

• New install: download ferry-1.0.2-docker-compose.tar.gz. It is not the program itself but the three files Docker Compose needs: compose.yaml, .env.example and the backup script. Compose then pulls the program, the public image ghcr.io/max1874/ferry:1.0.2, for linux/amd64 or linux/arm64.
• Already running 1.0.0 or 1.0.1? You do not need the download; see Upgrade.
• Source code (zip / tar.gz) is added by GitHub for developers. You do not need it to run Ferry.

What's changed

• Web downloads start at once. Clicking a file in the Web app used to fetch the whole file into the page before the browser saved anything, so a large file or a slow connection looked like nothing had happened. The browser's own downloader now saves the file, with its usual progress.
• Android in-app browsers can save files. Some apps' built-in browsers could not save the old in-page download and showed "No app can perform this action". The download is now an ordinary link on your Ferry server, which such a browser can hand to the system browser.
• How the link works. The Web app asks the Server for a link to one file. The link works for five minutes without signing in, only for that file, and stops working when the Server restarts or the device that asked for it is removed. The native apps download as before.
• License is MIT. The image label now says MIT, matching the repository.

Install

curl -fLO https://github.com/max1874/ferry/releases/download/v1.0.2/ferry-1.0.2-docker-compose.tar.gz
tar -xzf ferry-1.0.2-docker-compose.tar.gz
cd ferry
cp .env.example .env    # set FERRY_HOST_IP to this server's LAN IP
docker compose up -d
docker compose logs ferry

The README covers every step, other deployment paths and troubleshooting.

Upgrade

In your ferry directory, back up first:

scripts/ferry-data.sh backup ../ferry-backup-before-1.0.2.tar.gz

Change FERRY_IMAGE in .env to ghcr.io/max1874/ferry:1.0.2, then:

docker compose pull
docker compose up -d
docker compose logs --tail=100 ferry

Limits

• Ferry serves plain HTTP for a trusted private network. Keep it off the public Internet; a TLS reverse proxy of your own inside the private network is supported.
• Chrome and other Chromium browsers block downloads from a plain http:// address. Keep the file from the browser's download list, or allow "Insecure content" in the site settings for your Ferry address.

简体中文：https://github.com/max1874/ferry/blob/v1.0.2/docs/releases/1.0.2.zh-Hans.md

_{Image digest sha256:43daceb1059f0e3d287141e6372d0699d8aa6b23e30a1defc788735db3bf471a · commit 209e477 · CI run}

Ferry 1.0.1

Ferry 1.0.1 is a small update to the Ferry Server and Web app. Your messages, files, devices and password are not touched.

Which file do I need?

• New install: download ferry-1.0.1-docker-compose.tar.gz. It is not the program itself but the three files Docker Compose needs: compose.yaml, .env.example and the backup script. Compose then pulls the program, the public image ghcr.io/max1874/ferry:1.0.1, for linux/amd64 or linux/arm64.
• Already running 1.0.0? You do not need the download; see Upgrade from 1.0.0.
• Source code (zip / tar.gz) is added by GitHub for developers. You do not need it to run Ferry.

What's changed

• Redrawn app icon in the Web app.
• Clearer startup log in Docker. The first line now says that the address Ferry listens on is inside the container, so it is not mistaken for the address to open. The next line still names the address to open.
• No fixed time zone in compose.yaml. 1.0.0 set TZ: Asia/Shanghai, but the image carries no time-zone data, so the setting never took effect. Log times were and remain UTC.

Install

curl -fLO https://github.com/max1874/ferry/releases/download/v1.0.1/ferry-1.0.1-docker-compose.tar.gz
tar -xzf ferry-1.0.1-docker-compose.tar.gz
cd ferry
cp .env.example .env    # set FERRY_HOST_IP to this server's LAN IP
docker compose up -d
docker compose logs ferry

The README covers every step, other deployment paths and troubleshooting.

Upgrade from 1.0.0

In your ferry directory, back up first:

scripts/ferry-data.sh backup ../ferry-backup-before-1.0.1.tar.gz

Change FERRY_IMAGE in .env to ghcr.io/max1874/ferry:1.0.1, then:

docker compose pull
docker compose up -d
docker compose logs --tail=100 ferry

You can also delete the TZ: Asia/Shanghai line from your compose.yaml; keeping it changes nothing.

Limits

• Ferry serves plain HTTP for a trusted private network. Keep it off the public Internet; a TLS reverse proxy of your own inside the private network is supported.

简体中文：https://github.com/max1874/ferry/blob/v1.0.1/docs/releases/1.0.1.zh-Hans.md

_{Image digest sha256:a3dc11c83cc993d5408a2ed528a9f5df9c02bb0766be443d009c14b8ea5e84d5 · commit c7f10d7 · CI run}

Ferry 1.0.0

Ferry 1.0.0 is the first versioned release of the Ferry Server and Web app: a self-hosted timeline for moving text, links and files between your devices on a private network.

Which file do I need?

• To run Ferry, download ferry-1.0.0-docker-compose.tar.gz. It is not the program itself but the three files Docker Compose needs: compose.yaml, .env.example and the backup script. Compose then pulls the program, the public image ghcr.io/max1874/ferry:1.0.0, for linux/amd64 or linux/arm64.
• Source code (zip / tar.gz) is added by GitHub for developers. You do not need it to run Ferry.
• Phones and other computers need only a browser. The native iOS and Android apps are not published in this release.

What's new

• Install without cloning. The public image runs on 64-bit x86 and ARM servers, and the Compose download holds everything else.
• Connect another device. An empty timeline explains what to do next. Devices now shows the server address with a copy button and a QR code generated in your browser. The code carries only the address, never a device token or password.
• Clearer startup log. Ferry prints the address it listens on and, separately, the address to open in a browser, including a warning when that address works on this computer only.

Install

curl -fLO https://github.com/max1874/ferry/releases/download/v1.0.0/ferry-1.0.0-docker-compose.tar.gz
tar -xzf ferry-1.0.0-docker-compose.tar.gz
cd ferry
cp .env.example .env    # set FERRY_HOST_IP to this server's LAN IP
docker compose up -d
docker compose logs ferry

The README covers every step, other deployment paths and troubleshooting.

Upgrade an existing source deployment

In the directory you already deploy from:

scripts/ferry-data.sh backup ../ferry-backup-before-1.0.0.tar.gz
git pull --ff-only
docker compose pull
docker compose up -d

If your .env sets COMPOSE_FILE to build the source, remove compose.build.yaml from it first, keeping any override file, or Compose keeps building instead of using the image. The service, volume, data directory and user stay the same, so messages, files, device identities and the password carry over. Later upgrades change only the version in FERRY_IMAGE.

Limits

• Ferry serves plain HTTP for a trusted private network. Keep it off the public Internet; a TLS reverse proxy of your own inside the private network is supported.

简体中文：https://github.com/max1874/ferry/blob/main/docs/releases/1.0.0.zh-Hans.md

_{Image digest sha256:3eba51a1d91902543afd91c8f2c3eed85deb450d291a20d6b5599402e41a5bce · commit 84c355b · CI run}