☰ Expand overview

Faircamp 2

Released on September 23, 2026
Faircamp – Quick Info A static site generator for audio producers

Nine months of work. Over a hundred thousand lines of code revised, added or deleted. Version 2 is the biggest Faircamp release to date and brings Faircamp from the console to the desktop, introducing the new graphical site editor, a fundamentally overhauled architecture and dozens of bigger and smaller new features.

This release would not have been possible without the kind support of the netidee grant programme, who funded the majority of this work – thank you so much!

Finally, thank you to all supporters and the over 30 contributors to this release – your support made all the difference as well. <3

Automatic Migration to 2.0

It looks like you are opening a Faircamp 1.0 site directory. Would you like to automatically migrate it to 2.0?

- Your site will be migrated to a new directory
- Your original site directory will be left untouched
- Migration is fully automatic
- All noteworthy changes will be summarized in a report
- For best results your site should be error-free before migration

Faircamp can automatically migrate your site for use with 2.0 – it detects 1.x sites and opens a one-click wizard (desktop application) or suggests the needed command for migrating (CLI).

# Graphical desktop application

The launcher window featuring a header image, site bookmarks area, version information and links to the website and donation pages

Faircamp 2.0 introduces a graphical desktop application for editing and building Faircamp sites! This new interface coexists with the command line interface – both can be used interchangeably, even in parallel.

Main editor window (light theme)

Main editor window (dark theme)

Contextual actions in the navigation allow adding, removing or opening things in the file browser
Builds can be cancelled (and recontinued) anytime

Flat and tree navigation for different workflows

Tags derived from audio metadata are displayed as defaults in the respective setting fields

Toggleable log panel
Color swatches and sliders in the new faircamp 2.0 theme graphical theme settings

Interactive visual feedback is provided when adjusting theme settings

A graphical window menu with the items "Preprocess", "Build", "Build with Theming Widget", "Preview" and "Auto-preview each build"

You can do preview builds with the theming widget enabled from the graphical editor

# Accessibility of the desktop application

git 3
Keyboard navigation outline around a labelled checkbox in the Faircamp desktop application

The desktop application is fully navigable by keyboard. All screens should provide the most important landmarks for effectively navigating the application with assistive technology. All non-decorative visual elements of the interface should provide textual descriptions. There was no specific accessibility auditing yet though, so any problem reports, feedback and concrete suggestions for improvements are very welcome!

# Introducing the dedicated podcast layout

git 4
A faircamp release page, but some things are different: Much more space between tracks, release dates and synopsis texts for each track, etc.

Multitrack release pages now support two different presentation modes: The existing default album layout, and the new podcast layout. In the new podcast layout the track list includes synopsis texts, release dates, bigger track covers, differently formatted duration info and much wider spacing between tracks. Additionally its default ordering is reversed (newest tracks first), although this can be configured with the multitrack.order setting in both layouts now.

# Serving original audio formats for streaming and download

git 1
Download formats selector in the graphical editor, offering an "Original" option next to the regular MP3, Opus, etc. options

You can now use the "original" setting to serve your audio files to visitors in exactly the format that you supplied, both for streaming and/or download (or in other words, this setting bypasses transcoding).

# Label mode is gone – long live label mode!

git 1
A form field titled "Artist Attribution (site.artist_attribution)", offering the choices Enabled and Disabled. The label says "Display artists next to releases and tracks"

Label model has so far been Faircamp's monolithic way to switch from a presentation mode tailored for a single artist to one that is tailored for multiple artists/projects. Among other things, label_mode would display artist names in release overviews, auto-create pages for "main artists" while allowing further configuration through the feature_support_artists and show_support_artists settings, and enable further invisible routines relating to the automatic naming of the site and how links would lead you back to to the homepage.

In 2.0, label mode's functionality has been reimplemented through different mechanisms and settings, all with the aim of making the new approach more intuitive, granular and flexible. There are many interconnected aspects to this, but to name three cornerstones of this, going from conceptually overarching to specific:

1) In 2.0 a Faircamp site can not only present an artist or label, it can also present a single release, or even just a single track. If there is only a single track on your site, Faircamp will automatically feature it directly on the homepage now. Likewise, if your site contains multiple releases and a single artist that is its sole author, Faircamp will automatically turn the site into an artist site by making the artist page the homepage. And whenever you want to manually intervene in this, the explicit homepage setting (for artists, catalogs, multitracks and tracks) lets you do just that.

2) Whether an artist page is generated or not now rests on a simple core logic: If you explicitly create a directory and manifest for the artist – which is anyhow required to provide even just a link or one-liner for the artist – it gets its own page. There are no other magic rules for this anymore, no complex automation settings to discover and grasp regarding when artist pages are generated and when they aren't.

3) The artist_attribution setting now allows you to discretely control whether artists should be shown alongside releases in overviews, independent of whether the site is an "artist" or "label" site, or something else entirely.

# Introducing stand-alone tracks / "multitrack" is the new "release"

git 1
A folder hierarchy showing that track directories (directories containing a
track.eno file) can be placed both inside a multitrack directory (a directory
that contains a multitrack.eno file) as well as directly in the root of the
site directory (a directory that contains a site.eno file).

2.0 extends Faircamp's architecture, allowing for stand-alone tracks that do not need to be contained in a "release" anymore. As a track can now be a release in itself, what was formerly called "release" (something that contains tracks) is now called "multitrack".

Put another way: In 2.0 a single audio piece (a "single", an audiobook, etc.) is a "track" and it can stand on its own. When you have multiple tracks that belong together (tracks of an album, episodes of a podcast, etc.) you now wrap them into a "multitrack" (which corresponds to what was formerly called "release").

# Introducing adaptive mode for themes

git 3
Faircamp's footer with the new Darken/Lighten toggle switch

Previously you could set up your themes either as dark or light. 2.0 introduces a third mode: Adaptive theming. Configure both a dark and a light theme appearance at the same time (this also allows for different background images for each). When someone visits your page, their system preferences decide which theme they see – and they can also manually toggle between dark/light using a button in the footer. This mode is the new default. On migrated sites you can enable it through the theme.mode setting.

# Support for multiple, labelled external download links

git 3
Modal dialog with three buttons: Buy at Mirlo, Buy at jam.coop, Close

You can now specify multiple external download links for releases and tracks. Download links can optionally be labelled now.

# Visibility settings and conditional browse/search navigation

git 5
Select field labelled "Visibility" that offers four options:
Featured – openly accessible, included in browse/search
Public – openly accessible, excluded from browse/search
Unlisted – not listed anywhere, access requires knowing the URL
Offline – not included in the generated site

The new, unified visibility setting expands the previous unlisted/not unlisted state into four distinct states: Featured (openly accessible and included in browse/search navigation), Public (openly accessible but excluded from browse/search navigation), Unlisted (don't publicly link to item) and Offline (do not include in site). When all entities on a faircamp site are non-featured, the browse/search navigation automatically disappears.

# Non-streamable and no-audio tracks

git 1
Select field labelled "Streamable" that allows toggling between Allowing/disallowing streaming of the track

Tracks can now be explicitly set as non-streamable with the track.streamable setting or be created without an audio file to begin with (which can be added later too).

# Extended podcast settings and full spec compliance

git 3
Form fields for podcast settings

Categories (multitrack.podcast.categories)

Put each category on its own line, using the form 'Category' or 'Category > Subcategory', e.g.: 'Arts' or 'Arts > Visual Arts'.

Save/Cancel/Delete setting buttons.

Explicit Content (multitrack.podcast.explicit)

No explicit content

Override button.

You can now configure podcast.categories for your podcast feed(s). Explicit content can be tagged through podcast.explicit and is now communicated in podcast feeds (itunes:explicit). By default, streams are marked non-explicit.

# Universal Settings

git 1
Universal settings being shown in the docs, for instance demonstrating
how *.platform_integration corresponds to artist.platform_integration,
catalog.platform_integration, multitrack.platform_integration and
track.platform_integration at the same time.

The new universal settings allow you to set certain options across all objects to which they apply. For instance, instead of separately specifying download formats for multitrack and track objects with multitrack.download_formats and track.download_formats you can now specify *.download_formats to do it in one declaration.

# Tags

git 3
Tag settings opened in the desktop application, showing options like
track.tags.mode, track.tags.album, track.tags.album_artist, etc.

The tags setting has been split up into a new, subtly different constellation of settings, which now allow fine-grained control over tag rewriting without having to specify all tags that should be rewritten. For an overview take a look at tags.mode.

# New date/time metadata: released, published, updated

git 3
The new released/published/updated form fields in the graphical editor, alongside instructions for their currently unwieldy formats

Faircamp now has three new date/time metadata fields: released (the date of release on the faircamp site or anywhere else), published (the date/time of first publication on the faircamp site) and updated (the date/time of the last update of the respective item on the faircamp site).

These three new settings replace the former date setting and now also apply to tracks (released) or even artists, catalogs and tracks as well (published/updated). At this point they are mostly used for feeds, but in upcoming versions will likely also be used more widely and visibly on the site itself.

# New automatic and configurable homepage setting

git 6
A checkbox labelled "Homepage (artist.homepage)", The label says "Make this the homepage of your site"

Any page can be the homepage now – artist, catalog, multitrack or track. Faircamp automatically picks your homepage based on your content if you don't explicitly configure it, for instance: If you only have one release, it will be directly on the homepage by default. The permalink-based URL of any object now redirects to the homepage when an item is set as the homepage.

# Paycurtain without payment info

git 3
"Purchase downloads" page, displaying the text "You can pay using any of the
payment or donation links you find elsewhere on this page. If you can't find
any, get in touch!"

When you have enabled a paycurtain but not provided payment info, the paycurtain is now rendered anyway, containing a generic default text instructing users to look for payment or donations links on the site.

# Clean URLs are now opt-in

git 2

Faircamp now produces long-time-archiving-friendly builds, which are directly viewable from disk, out of the box. The site.clean_urls setting allows opting in to clean urls through a manifest setting now. Additionally, the --no-clean-urls flag allows overriding/disabling clean urls for (e.g.) the automatic creation of archivable builds in automated pipelines and backup routines.

# Speed controls as track-level setting

git 1
Close-up images of the docked player on two consecutive tracks, once with speed controls enabled, once disabled

Speed controls can now be enabled/disabled at the track level. The respective controls are rendered enabled/disabled in the player at runtime.

# Revised and customizable track ordering

git 2
Track Order dropdown in the Faircamp desktop application, showing a subset of
available options: Source Path, Title, Track Number, Update Date/Time, with
both an ascending and descending variant available for each.

Track order is now heuristically determined: If there are track numbers on most tracks, they control ordering. If there are release dates on even more tracks, they control ordering instead. Etc. Beyond this, ordering can be customized for each release, supporting many different ordering options: multitrack.order

# Expanded artist overrides

git 1

With the new defaults system you can override artists throughout the entire site (or for arbitrary subdirectories, etc.)

# A completely overhauled command line interface

git 4
Command line interface text from a help screen:
A static site generator for audio producers (Desktop edition)

Usage: faircamp [COMMAND]

Commands:
  build    Build a site
  cache    Manage cached assets
  clean    Delete directories created by faircamp
  docs     Open docs in the browser
  debug    Print debug information
  migrate  Migrate a site directory from v1 to v2
  preview  Build and preview a site in the browser
  tree     Experimental: Export or render a site tree
  help     Print this message or the help of the given subcommand(s)

Options:
  -h, --help     Print help
  -V, --version  Print version

To start the graphical editor pass no arguments at all

The command line interface has been cleaned up, improved and redesigned as a primarily command-based interface. For example: "faircamp" is now "faircamp build", "faircamp --preview" is now "faircamp preview", "faircamp --wipe-build" is now "faircamp clean build", etc. All prominent, accident-prone operations have been outfitted with safety confirmations, at the same time the new --non-interactive option allows disabling these prompts for use in fully automated scripts.

# Hotlinking protection settings merged

git 1

In 2.0 the previous freeze_downloads_urls and rotate_download_urls settings have been combined into a single url_seed setting.

# Documentation reboot

git 12
Search popup modal against a blurred background

The documentation has been completely overhauled for 2.0. Among other things it now includes an in-page navigation and search functionality (keyboard shortcut: "s"), which also allows searching by multiple keywords at once (seperated by space). One of the more notable additions in content is a stand-alone podcast example. Starting with the Faircamp 1.7 to 2.0 transition, archived documentation for previous versions will now be provided alongside that of the latest version. In other words, the documentation for 1.7 is and will stay permanently available at https://faircamp.org/docs/1.7.0/ and this will also apply for future versions as they are succeeded by newer ones.

# Releases, tracks and catalogs as external pages

git 1

The external_page setting is now available for catalogs, releases and tracks as well, allowing you to "outsource" releases, tracks, or entire catalogs to external pages, while still having them be discoverable through your faircamp site.

# Aliases and false aliases for artists

git 1

Artist aliases are now split into aliases (different artist names that connect to one artist and are always shown – a new setting) and false aliases (different names rewritten to a single name, the former alias setting).

# Site-wide links

git 1
Faircamp site footer showing arbitrary links like Imprint, Legal, Contact, etc.

The new site.links setting enables site-wide links, rendered in the footer.

# Simpler and shorter links syntax

git 2
Syntax comparison where in 1.x links used multiple lines per link, while in 2.0 only one line per link is used

The manifest syntax for declaring links has been greatly simplified. rel-me linking is now supported through the site.metadata setting using link tags rather than through links directly.

# Image description setting changes/improvements

Image descriptions are now represented as separate manifest settings git 1
Image descriptions now support both inline and multiline values git 1

# Feed and feed settings improvements

git 2

The "Generic RSS" feed is now called "Plain RSS", both for visitors on faircamp sites and in the respective setting. Furthermore the feeds setting now supports different, more versatile presets – textual feeds only, media feeds only, etc. Feeds now also make use of the newly introduced published and updated settings data.

# Favicon setting changes

git 1

Custom favicons must now be included through the site.assets and site.metadata setttings. The favicon setting itself has become a toggle to disable the native faircamp favicon: site.disable_favicon

# Cover generators

git 1
Three different generated covers in black-on-white or gray. Five of them are
some variant of a line, or multiple lines, circling or spiraling the center,
while scratching or erupting outwards in different ways and intensities. The
last cover looks like a giant pixelated monochrome and square graphic, just
squares of different medium-grey tones.

You can now configure the cover generator used for procedural covers using the theme.cover_generator setting (most choices are currently somewhat similar and on the experimental side though). Generated covers are fully opaque now, and generated either in their configured dark or light variant – this is not tied to the theme anymore. More diverse, fancy and polished cover generators will probably be added at some point in the future.

# New "Extras Label" and new default for extra downloads

git 2
Input field labelled "Extras-Label (Label for additional downloadable files)", someone has entered "Goodies"

Additional downloads can now be labelled in a custom way using the extras_label setting. The default availability of extra downloads is now bundled+separate (instead of just bundled).

# Platform Integration/Link Previews based on Open Graph

Note: Content embeds are currently only configurable, but not yet implemented

The "opengraph" setting is now the "platform integration" setting and includes "content embeds" (timeline player embeds) git 1
Link previews (formerly "opengraph") are now enabled by default git 1

# Theming widget refinements

git 1

Faircamp's theming widget now temporarily stores your changes for each theme and for dark/light mode separately, meaning that you can experiment with and switch back and forth between different settings in dark/light mode and across pages that already have a different theme according to the settings in your manifest(s).

# The catalog is gone – long live the site and its catalogs!

git 1

In 1.x everything revolved around the "catalog", which represented the entirety of your site, its global settings, as well as the homepage. In 2.0 this evolves in three ways:

Your faircamp site (in its entirety) is now simply called a "site", and with it, the catalog directory became the site directory. The main rationale behind this is 2.0's new flexibility: A Faircamp site can present arbitrary content now (right on the homepage), down to just a single track! "Catalog" would not describe this intended openness to different uses well anymore.

With catalog becoming site, the catalog.eno manifest became the site.eno manifest, and it now solely contains global settings – those that represent global metadata (title, url, etc.) and those that are inherited down to all items and pages on your site (for instance a global theme, or settings that should apply to all artist pages).

And that leaves one thing: Where did the catalog, as a homepage and overview of all releases, go? The answer depends on your usecase:

If you only present a single track, a single release, or multiple releases of a single artist on your site, your homepage can now simply be a track, release or artist page.

If you present releases by multiple artists, Faircamp will automatically create a (virtual) catalog page that it renders as homepage. If you want a "physical" catalog (home)page that you can edit, you can simply create one through a catalog directory and manifest – that is the new (old) catalog.eno file, now always in its own directory though. And what's more, you can now create multiple catalogs, and choose which one should be the homepage.

One last gotcha regarding the possibility for multiple catalogs: With the inital 2.0 release, catalogs always present all (public) releases of the site, and there isn't yet a possiblity to "filter" catalogs in order to present a different selection of releases in each – this however is planned for a future release.

# Introducing the new setting inheritance system

git 2

Faircamp 1.x (and 0.x before it) had partial, simple implementations of settings inheritance. While these worked very well for most usecases, they always came with one considerable gotcha – it was always either "this setting is passed down no matter what", "this setting is not passed down at all" or some bespoke inbetween logic to handle this in a special way on a case-by-case basis (intransparent and hard to predict).

2.0 comes with a new inheritance model that uses types to establish clear boundaries for inheritance. For instance: In the topmost site.eno manifest, a setting must always be prefixed with a type (artist, catalog, multitrack, or track) in order to be passed down. "artist.theme.mode: light" will enable the light theme for all artists on the site. "multitrack.theme.mode: light" will do the same for all multitrack releases on the site. If a setting should be set across all types there is also the universal prefix (*) – "*.theme.mode: light" will set the light theme across all pages on the site.

When we move to (e.g.) the settings (and manifest) of a multitrack release, there are yet more aspects to discover: Within the multitrack settings we can, but don't need to, use the "multitrack." prefix, because it is implied through the context. "theme.mode: light" enables the light theme for the multitrack, and so does "multitrack.theme.mode: light". However, in both cases the setting is not passed down to the tracks within the multitrack release – for this we would need to specify "track.theme.mode: light", which on its own would only specify a default to be passed down to all tracks, but not affect the theme of the multitrack release itself. The universal setting "*.theme.mode: light" would again be an option that allows us to specify both "multitrack.theme.mode: light" and "track.theme.mode: light" in one declaration.

Although this new model requires a bit of initial familiarization, it squares the circle, allowing to declare settings for either local-only use, inheritance-only use, or both. With the additional type-based filtering it further extends its practical use to previously unsupported applications. And: A great amount of effort went into making this system intuitively discoverable and usable through the graphical interface, which will (if successful) mean that users of the graphical editor will hardly have to think about the design of this (types, prefixing, etc.) and be able to just make use of it.

# Extended nesting possibilities and the new default manifests

git 2

Faircamp has always allowed you to group and organize almost everything in your site directory in arbitrarily nested folder hierarchies. In 2.0 this gets expanded in one more area: Track directories within a multitrack directory can now also be deeply nested. Think for instance about a podcast (multitrack) directory that contains (purely organizational) directories for each season, which then contain the (track) directories for all episodes of that season.

All of these purely organizational directories – which aren't themselves artist, catalog, multitrack or track directories – can now also contain so called default manifests. As the name already gives away, these manifests have a single purpose: You can specify any number of (artist, catalog, multitrack, track) default settings in them, which are then passed down to all directories and manifests nested below their directory.

# Track numbering refinements and new track number setting

git 2

Track numbers are now optional data – if none are provided, none are displayed on the site or included in the names of download files. Setting or overriding a track number is now possible through the new track.number setting. With the introduction of stand-alone tracks, track numbering can now be configured down to the track-level.

# Programmatic access to the site tree

git 2
  "artists": [
    "Iva Zabkar"
  ],
  "asset_basename": "Iva Zabkar - AOEO",
  "copy_link": true,
  "cover": {
    "content_hash": "FMNrCehccY0",
    "description": "Cover",
    "max_160": {
      "path": "/demo/.faircamp_cache/pzRSMIDP.jpg",
      "edge_size": 160,
      "size": 5090
    },
    "max_320": {
      "path": "/demo/.faircamp_cache/uJpuYfaN.jpg",
      "edge_size": 320,
      "size": 13862
    },
    "max_480": {
      "path": "/demo/.faircamp_cache/36QkQpi-.jpg",
      "edge_size": 424,
      "size": 20872
    },
    "max_800": null,
    "max_1280": null
  },
  "download_access": {
    "Paycurtain": {
      "price": {
        "currency_code": "USD",
        "currency_symbol": "$",
        "range": {
          "start": 0.0,
          "end": null
        },
        "user_representation": "USD 0+"
      },
      "payment_info": null
    }
  },
  "embedding": true,
  "external_page": null,
  "extra_downloads": "BundledAndSeparate",

2.0 introduces the --export-tree and --render-tree command line options.

With --export-tree you can instruct faircamp to output a JSON file that contains the entirety of the preprocessed site data, including references to all transcoded and prepared media files, ready for site generation.

With --render-tree you can point faircamp to a (previously exported) JSON tree file, instructing it to generate the site based on the preprocessed site tree stored in the file.

To learn more about this see the new Modding & Hacking section in Faircamp's documentation. Please note that the availability and format of this file is not considered stable at this point. While it's less likely that large structural changes will occur, it is very likely that implementation details will change. If you build on top of this and release such tooling to the public it is highly recommend to label it as experimental so people can make informed choices and not run into nasty surprises later on. Thank you for considering this!

# Progress reporting

Rewrite and improve hybrid (CLI/GUI) progress reporting git 2

# Robustness

Detect and report artist name/alias collisions git 1
Register tag reading failures (previously silently ignored and replaced with empty tags read) git 1
Propagate and gracefully handle io errors for cache, catalog, preprocessing and rendering git 1

# Performance

Use concurrent processing

Draft architecture and base implementation for graphical interface git 1
Isolate audio meta and waveform computation and only conditionally run when needed git 2

# Port auto-selection

Faircamp's new default preview port is 3247 ("Dial 127.0.0.1:FAIR") git 1
Faircamp now auto-selects its preview port from two different ranges (3247-3263, 8080-8096) git 1

# Translations

Welsh translations by Henry Young (on various buttons and links in an album page header)
Add welsh translations Henry Young git 1
Update Ukrainian translation before v2 beta Denys Nykula git 1
Update danish translations Jannis git 1
Update french translations Jérémie Bertrand git 1
Update lithuanian translations Vac git 2
Update catalan translations Ayman Hamad git 1
Update polish translations luce git 1
Update french translations Khawla A.G. git 1
Update spanish translations Eduardo Hernández Gil git 1
Update turkish translations atomkarinca git 1

# Image processing pipeline

git 1
An arrow pointing from a libvips title graphic to the Rust image crate logo

The image processing backend has been unified to use a pure rust solution (image). For now this comes with a small performance penalty (libvips is a bit faster) and small feature reduction (HEIF is not yet not supported in the image crate), but it greatly eases distribution and system compatibility for Faircamp, freeing up resources for actual development. Furthermore, the functionality gap between libvips and the image crate is likely going to close fast.

# Bugfixes

Update supported image formats constant, dynamically construct format filters with troschunk git 1
Use case-insensitive matching for Vorbis header comment keys with Baggypants, dheadshot git 2
Fall back to GET for failing HEAD requests during download code check with guesst git 1
Fix patchy logic for determining varying track artists on a release with incognitothief git 1
Print detailed debug reports for hard_link_or_copy failure cases git 1
Prevent console window creation during ffmpeg system calls on Windows with John Townshend git 1

# Misc

Generated asset filenames are now length-constrained to prevent overflowing maximum platform path length limits git 1
The faircamp website has moved to faircamp.org git 1
The desktop application is now the default build target git 1
The desktop application splash screen image can be customized for own builds git 1
Print dynamically retrieved name of current executable in usage hints with lnicola git 1
Differentiate between latest/stable version builds in build documentation with Wayne Myers git 1
Prelocate ffmpeg, parse/display version, report missing ffmpeg at runtime git 1
Add use-bundled-ffmpeg/force-bundled-ffmpeg features for bundled distribution git 2

# What had to be left behind

Faircamp was originally designed for command line use only, with the main interface being the folders, files and manifests inside your site directory. With 2.0 it became a hybrid system, supporting both the original filesystem interaction model, as well as interaction through a graphical interface.

Both approaches bring advantages, but also impose specific constraints on how the data model can be structured while still staying representable and comprehensible in both media – there must always be a common denominator.

For a small subset of the original data model it unfortunately proved unfeasible to establish that common denominator. They are:

Shortcut definitions of artists as they could be made in 1.x catalog and release manifests are not available in 2.0 anymore – they were incompatible with 2.0's consistent representation of all objects as nodes in the filesystem. In 2.0 artists are now always represented as directories with a manifest.

Artist manifests could previously live at the root of the site directory. In 2.0, they always need to be placed in their own directory. As with shortcut definitions this allows a consistent representation of artists as stand-alone filesystem nodes.

Releases (and their tracks) could previously be nested inside artists. Vice versa, artists could previously be nested inside releases and their tracks as well. 2.0 introduces a new settings inheritance system in which this kind of nesting would have produced very complex, barely representable (let alone understandable) relations between objects. To ensure usability of the system for everyone (not just graph theoreticians) the data model has therefore been flattened – artists and releases can now only be siblings.

Lastly, the --exclude <PATTERN> and --include <PATTERN> command line options were removed. While these were not at odds with the new data model, they depart somewhat significantly from Faircamp 2.0's general premise of being a hybrid system that is equally usable from the desktop and command line alike, instead representing its own CLI-centric workflow.

# All commits for this release
git 254