No description
  • Nix 86.3%
  • Python 6.7%
  • HCL 4.1%
  • Shell 1.9%
  • HTML 0.9%
  • Other 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Kiara Grouwstra 465c0df905 pass --extra-experimental-features explicitly in CI workflows (#844)
Don't assume the runner host has `nix-command` and `flakes` experimental features enabled in its nix config.
Pass them explicitly to all `nix` subcommands in CI workflows and in the generator script.

Reviewed-on: fediversity/fediversity#844
2026-04-23 14:31:02 +02:00
.forgejo pass --extra-experimental-features explicitly in CI workflows (#844) 2026-04-23 14:31:02 +02:00
checks simplify apps-* tests to delegate testing of specific applications to our services tests (#843) 2026-04-23 07:39:21 +02:00
keys fix/forgejo-ci-secrets-rekey (#825) 2026-04-20 21:37:33 +02:00
npins feat: pin Forgejo source from codeberg main development branch (#813) 2026-04-09 16:20:51 +02:00
panel expose schema over API (#808) 2026-04-06 20:14:55 +02:00
src tolerate SSH timeout in run.sh during switch-to-configuration (#839) 2026-04-22 20:29:10 +02:00
.envrc unify versioning (minus around nixops, for now) 2025-05-01 13:24:45 +02:00
.gitignore add .envrc files 2025-02-13 14:48:21 +01:00
default.nix tests: deploy > apps, apps runs too slow (#807) 2026-04-06 18:22:51 +02:00
flake.lock use data model (#597) 2026-03-02 20:01:06 +01:00
flake.nix use data model (#597) 2026-03-02 20:01:06 +01:00
LICENSE Initial commit 2024-10-02 12:13:02 +02:00
README.md readme: add edsger (#829) 2026-04-16 19:13:36 +02:00
shell.nix full-fledged-default-nix (#666) 2025-12-10 21:35:14 +01:00

The Fediversity project

This repository contains all the code and code-related files having to do with the Fediversity project.

Goals

Decentralise the operational responsibility for social media. Enable a more robust market of hosting providers, by making it easy to migrate operations and data to different providers.

Note that Fediversity is not about self-hosting. There already exist solutions for self-hosting, but they're not suitable for what we're trying to do. The ones we're aware of require substantial technical knowledge and time commitment by operators, especially for scaling to thousands of users. Not everyone has the expertise and time to run their own server.

Status: in development

see our:

Interactions

To reach these goals, we aim to implement the following interactions between actors (depicted with rounded corners) and system components (see the glossary, depicted with rectangles).

Actors

  • Fediversity project team

    The group working on this repository. We are creating the deployment workflows and service configurations.

    The project partners for Fediversity are:

    Refer to fediversity.eu for more details about the project.

  • Hosting provider

    They provide and maintain the physical infrastructure, and run the software in this repository, through which operators interact with their deployments. Hosting providers are technical administrators for these deployments, ensuring availability and appropriate performance.

    We target small- to medium-scale hosting providers with 20+ physical machines.

  • Operator

    They select the applications they want to run (Mastodon, Pixelfed, Matrix, etc.). They don't need to own hardware or deal with operations. Operators administer their services in a non-technical fashion, e.g. as moderators. They pay the hosting provider for registering a domain name, maintaining physical resources, and monitoring deployments.

    Initially, Fediversity is targeted at organisations, such as universities.

  • User

    They are individuals that are not necessarily affiliated with any organisation. They register an account on services (e.g. Mastodon) run by the operators, and e.g. post content. Users dont need to administrate anything.

    Given initial operators will be universities, users would be staff or students.

Glossary

  • Fediverse

    A collection of social networking applications that can communicate with each other using a common protocol.

  • Application

    User-facing software (e.g. from Fediverse) run by the hosting provider for an operator.

  • Configuration

    A collection of settings for a machine running NixOS.

    Example: Configurations are deployed to VMs.

  • Provision

    Make a resource, such as a virtual machine, available for use.

    Example: We use Proxmox to provision VMs for applications run by operators.

  • Deploy

    Put software, such as applications, onto computers. The software includes technical configuration that links software components. Most user-facing configuration remains untouched by the deployment process.

    Example: OpenTofu is used to deploy Pixelfed.

  • Migrate

    Move service configurations and deployment state, including user data, from one hosting provider to another.

  • Runtime backend

    A type of digital environment one can run operating systems such as NixOS on, e.g. bare-metal, a hypervisor, or a container runtime.

  • Runtime environment

    The thing a deployment runs on, an interface against which the deployment is working. See runtime backend.

  • Runtime config

    Configuration logic specific to a runtime backend, e.g. how to deploy, how to access object storage.

Development

All the code made for this project is freely licenced under EUPL. This means, anyone can use the work here to learn from it or change it according to their needs. You can even read up on development proceedings.

Contact the project team if you have questions or suggestions, or if you're interested in using Fediversity software for your operations:

Content of this repository

Most of the directories in this repository have their own README going into more details as to what they are for. As an overview:

  • keys/ contains the public keys of the contributors to this project as well as the systems that we administrate.

  • panel/ contains the code of our front-end.

  • src/ contains source code handling deployments.

Usage

Loading the nix shell should install a pre-commit hook.