Portainer Templates logo

Portainer Templates

Filegator Filegator

Stack

Files

FileGator is a free, open-source, self-hosted web application for managing files and folders.

Image details

Pulls: 755k
Architecture: amd64, arm64, arm/v7, 386
Image size: 197 MB
Latest: v7.15.1-multiarch
User: filegator
Created: Oct 10, 2022
Updated: 2 days ago
Status: active

Source details

Repo: filegator/filegator
Stars: 3k
Forks: 444
Language: PHP
License: MIT
Latest: v7.15.1 · 2 days ago
Updated: 12 hours ago
Website: filegator.io/

Configuration

Type
Compose
Platform
linux
Image
filegator/filegator:latest
Ports
8886:80
Volumes
/srv/files : /mnt/MYSMBMOUNT/config : /portainer/Files/AppData/Config/filegator/data
Restart
unless-stopped
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Filegator

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Filegator, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  filegator:
    image: filegator/filegator:latest
    container_name: filegator
    ports:
      - "8886:80"
    volumes:
      - /mnt/MYSMBMOUNT:/srv/files:shared  # Bind your SMB mount
      - /portainer/Files/AppData/Config/filegator/data:/config  # Persist config
    restart: unless-stopped

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/filegator.yml up -d

More install options in our documentation, or see filegator/filegator for app-specific guidance.

FileGator - Powerful Multi-User File Manager

FileGator is a free, open-source, self-hosted web application for managing files and folders.

Documentation

https://docs.filegator.io/

Source code

https://github.com/filegator/filegator

Dockerfile

https://github.com/filegator/filegator/blob/master/Dockerfile

Run filegator with a persistent volume as a main repository

docker run -d \
           -p 8080:8080 \
           -v my_volume:/var/www/filegator/repository \
           --name filegator \
           filegator/filegator:latest

visit: http://127.0.0.1:8080
login as admin/admin123

Multiarch (arm)

Multiarch image is built using this file without ldap adapter due to compatibility issues 
filegator/filegator:latest-multiarch

Live Demo

Demo: https://demo.filegator.io Souce: https://github.com/filegator/demo

Sample docker-compose.yml file 

version: '2'
services:
  filegator:
    container_name: filegator
    image: filegator/filegator
    restart: always
    ports:
      - "8080:8080"
    volumes:
      # common mount points are listed here
      # make sure filegator can read/write to the mounted volume

      # mount local folder as a repository
      - ./files:/var/www/filegator/repository

      # locally stored users.json file
      # - ./users.json:/var/www/filegator/private/users.json

      # load your own custom configuration file
      # - ./configuration.php:/var/www/filegator/configuration.php

Note: for better security, filegator runs as a www-data user. To fix potential file permission issues, you can try changing the mounted volume permissions from within:
docker exec -u root filegator chown -R www-data:www-data /var/www/filegator/repository/

Serve Filegator on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying filegator.example.com to http://filegator:80

Add this to your Caddyfile

filegator.example.com {
	reverse_proxy http://filegator:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8886 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8886
  • Stop the other service, or pick a different host port. In 8886:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8886. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, filegator can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8886

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /mnt/MYSMBMOUNT (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull filegator/filegator:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, 386
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Filegator is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Filegator needs bundled into one download. This template pulls filegator/filegator:latest, which Docker fetches once (about 197 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Filegator's comes from Docker Hub, published by filegator.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v7.15.1-multiarch. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, 386, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 8886:80 means it's reachable on port 8886 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8886 in a browser. It opens:

  • 8886:80, likely the web interface

Volumes

A volume is where Filegator keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /srv/files from /mnt/MYSMBMOUNT on the host
  • /config from /portainer/Files/AppData/Config/filegator/data on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Filegator after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Filegator sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container filegator. That's what you'll spot in the containers list and use in commands like docker logs filegator.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Filegator is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Filegator up. Add the template list to Portainer once, then deploying Filegator is a click rather than a wall of config.