Target: Demo at Fediforum online conference 2025-04-01

Goal

Demo the key aspects of Fediversity:

The point of the demo is to communicate:

That the project extists, what it is about, how it's special, and that it's progressing towards its goals
That this is the infrastructure you can use to provide a micro-cloud to end users
The ultimate goal is infrastructure portability
That we care about technological and economic sustainability
For organisations that want to participate in the Fediverse, we may be a good partner

Target audiences:

There are ~47 (~9weeks) workdays between 27-01-2025 and 01-04-2025.
Demo users will use the Fediversity infrastructure.

There are a few things we have to hard-code for now, so the backend setup won't be easily adopted by others, and this isn't the goal for the demo. Eventually we'll also need to describe the infrastructure one needs to run the whole thing.
At this point it's not clear if we'll manage to enable service portability.

Services ready to run on top of Garage: PeerTube, Mastodon, Pixelfed. Making them portable is fairly involved though.

Galene doesn't have any state and only needs configuration files to be ported over. But it doesn't have a NixOS service yet. Likely we we'll only need the Nix expression once we have it.

Set up a Django CRM service (as discussed 2024-11-06)
Trigger NixOps4 on form submission:
Requires a provider for the NixPanel to store deployment state and send progress updates
Requires a Passbolt provider for dynamic secrets (as discussed regarding secrets handling 2024-12-10)
First step: assume a fixed provisioned setup
For (optional) migratio: VM provisioning will be handled via Ansible for now:
- A NixOps4 Terraform provider is currently planned but will not be ready in time
Rebrand MyProtagio to Fediversity
- Remove the intermediate registrar and register DNS domains ourselves
- Demo users will register an actual domain (and a bulk service package) using a voucher token