Install fdroidserver with Homebrew, apt, MacPorts, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• fdroid

Project history

F-Droid says the project was founded in 2010 by Ciaran Gultnieks. fdroidserver began as the complete server-side setup that ran f-droid.org, but its README explains that the website and other pieces were later split into separate projects while the fdroidserver name remained for the tooling suite.

The fdroidserver README describes the project as tools for maintaining an F-Droid repository system. It is used to maintain the f-droid.org application repository, to create alternative repositories, and to help create, test, and submit metadata to fdroiddata.

The project lives in F-Droid's GitLab namespace and has long-running branches and merge requests because the production f-droid.org setup runs directly from master on a regular schedule. Stable releases are also provided, mainly for custom repositories and for contributors who want packaged tooling.

Adoption history

fdroidserver's adoption follows F-Droid's role as the free-software Android app repository. Anyone publishing an F-Droid-compatible repository needs the same primitives: app metadata, APK handling, signing keys, index generation, and deployment. fdroidserver packages those primitives into the fdroid CLI.

The supplied package facts show fdroidserver in Homebrew, Debian, MacPorts, Nix, and Ubuntu. That cross-platform packaging is important because repository maintainers and app contributors often work from ordinary desktop or CI environments rather than from a dedicated server.

F-Droid's own about page positions the ecosystem as privacy-respecting, account-free, open, and community-run. fdroidserver is the infrastructure-facing half of that promise: it makes app distribution auditable and reproducible enough for a community repository and for third-party repositories.

How it is used

Typical usage is through the fdroid command to initialize and maintain a repository, process app metadata, build packages, update repository indexes, and deploy signed repository data. The current curation records config.yml in a repository directory and a default keystore path under ~/.local/share/fdroidserver.

The tool is also part of the contributor workflow for fdroiddata. Maintainers can test metadata and builds locally before submitting changes to the public F-Droid app collection.

Why package nerds care

fdroidserver is package-manager machinery in the purest sense: metadata, signatures, indexes, build recipes, repository publishing, and policy checks. For package nerds, it is the Android-world analogue of distro repository tooling, with extra attention to source availability and user freedom.

It also explains why F-Droid is more than an APK download site. The server tools embody the reviewable supply chain: build metadata, reproducible-ish processes, signed indexes, and independent repository creation.

Timeline

• 2010: F-Droid project founded.
• 2014: fdroidserver GitLab project created in the F-Droid namespace.
• 2019: fdroidserver 1.1 appears in release tag history.
• 2021: fdroidserver 2.0 released.
• 2026: fdroidserver 2.4.5 appears in release tag history.

Related projects

• fdroiddata contains app metadata for the public F-Droid repository.
• F-Droid Client is the Android app-store client that consumes repositories produced by the server tooling.
• Repomaker and other F-Droid ecosystem tools build on the same repository model.

Sources

• https://f-droid.org/en/about/
• https://gitlab.com/fdroid/fdroidserver
• https://gitlab.com/fdroid/fdroidserver/-/raw/master/README.md
• https://f-droid.org/en/docs
• https://formulae.brew.sh/formula/fdroidserver