Docs / How-to guides

Run KEIBIDROP on a NAS

The box serves a folder around the clock. Your computer mounts it on demand, wherever it is.

Use it for

A KEIBIDROP session needs both machines online. A NAS or a home server is online all the time, so it can be the serving side: footage on the studio box, the archive in the rack, a working folder reachable from any laptop. The box shares the folder. Your computer mounts it with the KEIBIDROP app and reads it on demand, end to end encrypted. Only the bytes a program reads cross the wire.

The container holds the serving side only, so it runs on plain Docker with the stock kernel and standard container permissions. The driver (macFUSE, fuse3 or WinFsp) lives on the machine that reads the files, your computer, set up per the install guides.

What the box needs

Start it

Save this as docker-compose.yml, set the path of the folder to serve, and start it:

services:
  keibidrop:
    image: ghcr.io/keibisoft/keibidrop:latest
    container_name: keibidrop
    restart: unless-stopped
    network_mode: host
    environment:
      KEIBIDROP_PEER: ""            # your computer's 86-character code, or pair later
      KEIBIDROP_PEER_NAME: laptop
      KEIBIDROP_SHARE_READ_ONLY: "false"
    volumes:
      - /path/to/your/files:/shares
      - keibidrop-config:/config
volumes:
  keibidrop-config:

docker compose up -d
docker compose logs -f

The log prints the box's own code and the pairing steps. That is the whole configuration on the box. On Unraid, the template in the repository under docker/unraid exposes the same settings in the Docker tab. The image is ghcr.io/keibisoft/keibidrop, published with each release since 0.4.4 for amd64 and arm64. docker build -f docker/Dockerfile -t keibidrop:local . builds it from the repository as well.

Examples

Camera to box: Sony, Canon and Nikon bodies send each shot over FTP to a Synology or a QNAP at the studio, or a card reader drops the cards into a folder on the box. That folder is the one the laptop sees.

Photos: Lightroom Classic adds the raws from the folder in place, with Add instead of Copy; the catalog and the previews stay on the laptop. Capture One works the same way with referenced files.

Video: DaVinci Resolve, Premiere Pro and Final Cut Pro point their media at the folder; the project library, the project file or the Final Cut library stays on the laptop. Scrubbing pulls the parts of the clip you touch. The video and audio guide has the details per application.

Archive: a home server keeps the archive on the box with the share set read only, and every computer in the house mounts it.

Networking

With host networking and IPv6 on both ends, the connection is direct. When one side blocks inbound connections, which is the normal state of a laptop on home WiFi, the traffic goes through the bridge, which forwards encrypted bytes it cannot read. A direct connection never uses relay credit; bridged traffic rides the free tier until credit is added. KEIBIDROP_STRICT: "true" turns the fallback off and fails the connection instead. The full picture, including a self-hosted relay, is in work through firewalls and the network and ports reference.

Limits

• A session is exactly two peers. One box serves one computer at a time.
• The box's uplink bounds a full copy. Opening a file is quick because only the touched blocks move; exporting all of it is a normal upload at the box's upload speed.
• Application catalogs and databases (Lightroom, Resolve, SQLite files) stay on the computer that runs the application, as in hand a database between machines. Media streams over the mount.
• After a session ends, the box waits about 90 seconds before it opens its room again. A reconnect started inside that window can report the box as not found. Connect again.
• Every setting from the configuration reference also works through /config/config.toml; environment variables win over the file.