filebrowser/skills/filebrowser-layer/SKILL.md
FileBrowser Quantum web file manager on port 8080 with config-file-driven setup. Use when working with FileBrowser, web file management, or file browsing in containers.
npx skillsauth add overthinkos/overthink-plugins filebrowser-layerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | supervisord |
| Ports | 8080 |
| Volumes | data -> ~/.filebrowser/data, files -> ~/.filebrowser/files |
| Service | filebrowser (supervisord) |
| Install files | task:, config.yaml |
| Variable | Value |
|----------|-------|
| FILEBROWSER_CONFIG | /etc/filebrowser/config.yaml |
| Name | Command |
|------|---------|
| filebrowser | filebrowser |
FileBrowser Quantum (gtsteffaniak fork, v1.2.4-stable) is config-file driven -- it uses
/etc/filebrowser/config.yaml, NOT CLI flags like classic filebrowser. The FILEBROWSER_CONFIG
environment variable points to the config file.
Default credentials: admin / admin. Change immediately after first login via the web UI.
Database and cache stored in the data volume (~/.filebrowser/data/database.db).
User-accessible files served from the files volume (~/.filebrowser/files).
The files volume is typically bind-mounted to a host directory at deploy time:
charly config filebrowser --bind files=~/Documents
charly config filebrowser --bind files=/mnt/nas/shared
# charly.yml
filebrowser:
base: fedora
candy:
- agent-forwarding
- filebrowser
- dbus
- charly
ports:
- "8085:8080"
Tunnel config is in charly.yml: tunnel: {provider: tailscale, private: all}. See /charly-core:deploy.
/charly-filebrowser:filebrowser/charly-infrastructure:supervisord -- process manager dependency/charly-infrastructure:traefik -- similar pattern (binary download + config file + supervisord)/charly-infrastructure:dbus-layer -- D-Bus session bus (co-deployed in filebrowser box)/charly-tools:charly -- charly CLI (co-deployed in filebrowser box)/charly-core:charly-config -- deployment configuration, --bind files=<path> for file volume/charly-core:start -- start the service/charly-core:shell -- interactive access to the containerUse when the user asks about:
FILEBROWSER_CONFIG configuration/charly-image:layer — candy authoring reference (charly.yml schema, task verbs, service declarations)/charly-check:check — declarative testing (check: block, charly check box, charly check live)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).