Filestash — a web file manager and universal front-end for your storage: browse, upload, preview, and edit files across S3, SFTP, FTP, WebDAV, Git, local disk, and more, all from one UI with sharing links. Deployed as a host-networked Nomad service with a persistent config volume.
Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.
Source ↗ Project ↗ ★ 14.7k ⚑ Report an issue
Save as values.hcl, edit, then run:
# The name of the Nomad job.
job_name = "filestash"
# The Nomad namespace to deploy into.
namespace = "default"
# The datacenters to deploy to.
datacenters = ["*"]
# The Filestash container image. Pin a tag in production.
image = "machines/filestash:latest"
# Host port for the Filestash web UI. The container listens on 8334.
port = 8334
# Public URL Filestash is served at (APPLICATION_URL), used for share links. Empty = derive from the request.
application_url = ""
# Named volume for Filestash config and state (/app/data/state): the admin config, SQLite, and search index.
data_volume = "filestash_data"
# Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []
# Resources for the Filestash task.
resources = {
cpu = 500
memory = 512
}
| Name | Type | Default | Description |
|---|---|---|---|
| job_name | string | "filestash" | The name of the Nomad job. |
| namespace | string | "default" | The Nomad namespace to deploy into. |
| datacenters | list | ["*"] | The datacenters to deploy to. |
| image | string | "machines/filestash:latest" | The Filestash container image. Pin a tag in production. |
| port | number | 8334 | Host port for the Filestash web UI. The container listens on 8334. |
| application_url | string | "" | Public URL Filestash is served at (APPLICATION_URL), used for share links. Empty = derive from the request. |
| data_volume | string | "filestash_data" | Named volume for Filestash config and state (/app/data/state): the admin config, SQLite, and search index. |
| constraints | list | [] | Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true". |
| resources | object | {
cpu = 500
memory = 512
} | Resources for the Filestash task. |
No variables match.
This pack stores data in one Docker named volume:
filestash_data
restic
# Run on the node hosting this pack. Point restic at your repo first: # export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>" # export RESTIC_PASSWORD="<repo-password>" # export AWS_ACCESS_KEY_ID=<key> AWS_SECRET_ACCESS_KEY=<secret> restic backup \ /var/lib/docker/volumes/filestash_data/_data
rclone (sync to S3/R2)
rclone sync /var/lib/docker/volumes/filestash_data/_data backup:<bucket>/filestash_data
Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.
Filestash — a web file manager and universal front-end for your storage. Browse, upload, preview, and edit files across S3, SFTP, FTP, WebDAV, Git, local disk and more, all from one clean UI, with sharing links, an org-mode/markdown editor, and image/video/office previews.
Single host-networked Nomad service with a persistent config/state volume.
nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run filestash --registry=nomploy
| Variable | Default | Description |
|---|---|---|
port |
8334 |
Web UI port. The container listens on 8334. |
application_url |
"" |
APPLICATION_URL — set to your public URL so share links are correct. |
data_volume |
filestash_data |
/app/data/state — admin config, SQLite, search index. |
image |
machines/filestash:latest |
Container image. Pin a tag in production. |
resources |
{ cpu = 500, memory = 512 } |
Task resources. |
On first run, open /admin to set the admin password, then add storage backends. Filestash is a
front-end — it connects to storage you already have (great paired with the seaweedfs or minio packs
over S3). Serves plain HTTP — front it with a reverse proxy for TLS. Pin the job to the node holding the
volume with constraints.