Every time I come home from a shoot, the same thing happens: before I’ve even reached the door, the messages start — “Can you share the photos?” Friends, family, the people who were in the frame. I love that they want them, but sending full-resolution images over chat apps (which compress them) or setting up a cloud link for each person got old very quickly.

I wanted something simple, quick, and under my control. While searching for a tool that could do the job, I found FileGator — and it’s awesome.

What FileGator is

FileGator is a free, open-source, self-hosted web file manager. You point it at a directory, and it gives you a clean browser UI to upload, download, and organise files. No desktop client, no accounts on someone else’s platform — just a web page on my own server.

Why it fits my photo workflow

The feature that sold me is per-user home directories. Each user I create can be locked to their own folder, so:

  • The family gets a family/ folder with the photos from our trips.
  • Friends from a photo walk get a folder with just that day’s shoot.
  • Nobody sees anything that isn’t meant for them.

On top of that, each user gets their own permissions — read, write, upload, download, zip, and so on. Most of my users are download-only: they can browse the folder and grab the full-resolution photos (or download a whole album as a zip), but they can’t delete or change anything.

So my routine is now:

  1. Come home, copy the edited JPEGs into the right folder.
  2. Send a link and the user’s login.
  3. Done — they download at full quality, whenever they want.

The build

FileGator ships an official Docker image, so it slots right into my homelab next to my other containers.

docker-compose.yml

services:
  filegator:
    image: filegator/filegator:latest
    container_name: filegator
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      # The folders I share — this becomes FileGator's repository.
      - /srv/photos/shared:/var/www/filegator/repository
      # Keeps users, permissions, and settings across container updates.
      - /srv/filegator/private:/var/www/filegator/private

Bring it up:

docker compose up -d

Then open http://<host>:8080, log in with the default admin account, and change the admin password straight away. From the Users screen I create one user per person or group, set their home directory (for example /family), and tick only the permissions they need.

A few things I learned

  • Change the default credentials first. It’s the very first thing to do on any self-hosted app.
  • Persist the private folder. That’s where FileGator stores its users and settings. If it isn’t on a volume, a container update wipes your users.
  • Share exports, not masters. I only put edited JPEG exports in the shared folder — my RAW originals stay somewhere FileGator never sees.
  • Don’t expose it naked. If you open it to the internet, put it behind a reverse proxy with TLS.

Where I am now

Photo requests used to feel like a chore after a long day of shooting. Now they take a minute. I’m happy with it — and I’m still on the lookout for more small, focused tools like this that solve one problem really well.