ov-filebrowser/skills/filebrowser/SKILL.md
FileBrowser Quantum web file manager with Tailscale tunnel. MUST be invoked before building, deploying, configuring, or troubleshooting the filebrowser image.
npx skillsauth add overthinkos/overthink-plugins filebrowserInstall 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.
Web file manager accessible via Tailscale private tunnel.
| Property | Value | |----------|-------| | Base | fedora | | Layers | agent-forwarding, filebrowser, dbus, ov | | Platforms | linux/amd64 | | Ports | 8085:8080 | | Tunnel | tailscale (private: all) | | Registry | ghcr.io/overthinkos |
fedora (base)pixi -> python -> supervisord (transitive)agent-forwarding -- SSH/GPG agent forwardingfilebrowser -- web file manager, data + files volumesdbus -- D-Bus session busov -- ov CLI inside container| Port | Service | Protocol | |------|---------|----------| | 8085 (host) -> 8080 (container) | FileBrowser | HTTP |
| Name | Path | Purpose | |------|------|---------| | data | ~/.filebrowser/data | Database (SQLite) and cache | | files | ~/.filebrowser/files | User-accessible files (bind-mount target) |
ov image build filebrowser
ov config filebrowser --bind files=~/Documents
ov start filebrowser
# Access at http://localhost:8085
# Tailscale: https://<hostname>:8085
# Default login: admin / admin
# Browse home directory
ov config filebrowser --bind files=~/
# Browse NAS mount
ov config filebrowser --bind files=/mnt/nas/shared
# Browse specific project
ov config filebrowser --bind files=~/projects
ov alias install filebrowser
# Now: filebrowser (runs inside the container)
/ov-filebrowser:filebrowser -- FileBrowser Quantum service, config, volumes/ov-foundation:agent-forwarding -- SSH/GPG agent forwarding/ov-foundation:dbus -- D-Bus session bus/ov-foundation:ov -- ov CLI for in-container management/ov-foundation:fedora -- parent base image/ov-ollama:ollama -- similar simple service patternAfter ov start:
ov status filebrowser -- container runningcurl -s http://localhost:8085 -- web UI responds (HTTP 200)curl -s http://localhost:8085/health -- {"message":"ok"}https://<hostname>:8085 from any tailnet deviceLatest ov eval live filebrowser run: 24 passed, 0 failed, 0 skipped.
All tests embedded in the org.overthinkos.eval OCI label, covering
agent-forwarding prerequisites (gpg, ssh, direnv binaries), supervisord
127.0.0.1:${HOST_PORT:8080},
HTTP 200 on /, data volume mounted.See /ov-build:eval for the framework and author-facing gotchas.
/ov-filebrowser:filebrowser — layer authoring/ov-build:eval — declarative testing framework/ov-core:config — deploy-mode setup with volume backing and tunnels/ov-build:build — LABELs-at-end cache efficiencyMUST be invoked when the task involves the filebrowser image, web file management deployment, or the FileBrowser Quantum service. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)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).