filex

Overview ¶

client.go wires the `filex client` subcommand family — a CLI consumer of a REMOTE filex server's REST API (the rest of the binary manages a local instance). Connection resolution, wire calls and mv semantics live in internal/cliclient; this file is cobra plumbing + rendering.

Command filex is the self-hosted file-manager binary.

Default behavior (`filex` with no args) is to start the HTTP server. All subcommands accept --config /path/to/config.yaml (or FILEX_CONFIG env).

filex serve                                 # default
filex migrate up | down | status
filex admin reset-password [--email]
filex admin random-password [--email]
filex storage list | add | remove
filex thumb backfill [--storage <id|name>] [--limit N] [--retry-failed]
filex client login | ls | upload | download | mkdir | rm | mv | search | share
filex e2e-escrow keygen                      # install-time E2E key escrow
filex --version

mount.go wires the `filex mount` subcommand: a remote filex server, attached to a folder on this machine.

It is the third answer to "let me use filex as a drive", and the one that works from anywhere: NFS needs a LAN, SFTP needs sshfs or WinFsp installed and configured, and this needs the same HTTPS and the same session token the web app already uses. Authentication, ACLs, the tenant scope and reach through whatever proxy sits in between all come for free, because underneath it is the REST API.