Installer faircamp avec Homebrew, apk, Nix

Liens du projet

• Page d'accueil

Commandes et alias

• faircamp

Historique du projet

The public changelog shows Faircamp developing quickly through 0.x releases in 2023 and 2024, reaching 1.0 on December 26, 2024. Its README frames the project around a simple publishing promise: point the tool at an audio catalog and get a complete website with downloads, playback, metadata, and hosting portability.

After 1.0, the project continued adding music-site features rather than becoming a generic static-site generator. Release notes in 2025 describe track directories, release and track manifests, feeds, embedded players, browse/search behavior, translations, link and timecode support, and custom site assets and metadata.

Faircamp's development has also been institutionally backed. The README states that Faircamp 1.0 through 1.4 was financed and supported by the European Commission's Next Generation Internet programme through NGI0 Entrust and NLnet, while major 2.0 work in 2026 is funded by netidee.

Historique d'adoption

Faircamp's adoption story is tied to independent music publishing rather than general web development. The official site and README point to community resources and a showcase of sites using Faircamp, and the changelog shows contributions from translators, bug reporters, and audio-site users across 2025.

Package-manager availability remains modest but visible: the supplied facts list Homebrew, Alpine, and Nix. That fits the tool's audience: artists or labels can install one CLI, keep catalog metadata next to audio files, and publish static output to ordinary web hosting.

Modes d'utilisation

A normal Faircamp project is a catalog directory containing audio and optional manifests such as `catalog.eno`, `artist.eno`, `release.eno`, and `track.eno`. The manual describes these manifests as the way a site is tweaked, configured, extended, and themed.

The generated output is intentionally static. That makes Faircamp attractive where creators want Bandcamp-like presentation, playable releases, downloads, feeds, and embeds without maintaining a dynamic web application or giving up control of hosting.

Pourquoi les passionnés de paquets s'y intéressent

Faircamp is package-nerd-relevant because it packages a whole independent-music publishing workflow into one CLI. It is a modern example of a domain-specific static generator: not a framework, not a CMS, just a reproducible command over files on disk.

Its manifest-based design also makes it friendly to version control and package-managed installs. The interesting part for maintainers is keeping the binary, docs, examples, generated assets, and audio-format support in sync across desktop platforms while the upstream project moves quickly.

Chronologie

• 2023: Early 0.x releases appear in the official changelog.
• 2024-12-26: Faircamp 1.0 released.
• 2025-02-11: Faircamp 1.2 introduced track directories and new release/track options.
• 2025-04-10: Faircamp 1.3 added Podcast RSS and Atom feeds plus player and timecode-linking features.
• 2025-04-22: Faircamp 1.4 added custom assets and metadata.
• 2025-11-16: Faircamp 1.7 released.
• 2026: Major Faircamp 2.0 work funded by netidee.

Related projects

• Bandcamp, static-site generators, Eno manifests, audio catalog publishing tools

Sources

• https://codeberg.org/simonrepp/faircamp
• https://codeberg.org/simonrepp/faircamp/raw/branch/main/README.md
• https://codeberg.org/simonrepp/faircamp/raw/branch/main/CHANGELOG.md
• https://faircamp.org/docs/latest