fediversity/fediversity

Watch

Fork 10

[D2.2] Software release beta version [2027-03-31] #483

New issue

Open

opened 2025-07-30 09:03:13 +02:00 by kiara · 1 comment

kiara commented

2025-07-30 09:03:13 +02:00

Owner

The release of a set of instructions, documentation and reproducible Nix-packages that together build a beta test production environment for hosting multiple Fediverse programs (at least, but not limited to Mastodon, Peertube and Pixelfed) and possible supporting software (like dns-servers, mailservers and authentication mechanisms).
Iteration based on deliverable D2.1 (#640)

> The release of a set of instructions, documentation and reproducible Nix-packages that together build a beta test production environment for hosting multiple Fediverse programs (at least, but not limited to Mastodon, Peertube and Pixelfed) and possible supporting software (like dns-servers, mailservers and authentication mechanisms). > Iteration based on deliverable D2.1 (#640)

kiara added this to the WP-D-2.2 Software release beta environment milestone

2025-07-30 09:03:13 +02:00

kiara added the

type

key-result

label

2025-07-30 09:03:13 +02:00

kiara added a new dependency

2025-07-30 09:04:50 +02:00

#314 ephemeral state is automatically provisioned

kiara added a new dependency

2025-07-30 09:05:20 +02:00

#116 hypervisor resources are provisioned to deploy services to

kiara added a new dependency

2025-07-30 09:06:01 +02:00

#313 back-end supports multiple users

kiara added this to the Fediversity project

2025-08-02 16:43:34 +02:00

kiara added a new dependency

2025-08-02 16:44:08 +02:00

#69 Separate test environments for staging vs. production

kiara referenced this issue

2025-09-13 13:27:28 +02:00

implement a way to run online services emphasising user autonomy and data portability #347

kiara changed title from ~~[month 24] Software release beta version~~ to [D2.2, month 24] Software release beta version

2025-12-02 13:10:57 +01:00

kiara changed title from ~~[D2.2, month 24] Software release beta version~~ to [D2.2] Software release beta version [2027-03-31]

2025-12-04 22:12:52 +01:00

kiara referenced this issue

2025-12-04 22:20:53 +01:00

[D2.3] brought into production [2027-11-01] #228

kiara added

and removed

labels

2025-12-11 14:26:12 +01:00

kiara added a new dependency

2026-08-09 16:29:40 +02:00

#225 kick-started initial feedback cycle

kiara commented

2026-10-01 10:35:52 +02:00

Author

Owner

note that ProcoliX in a production setting has intended for things to work out-of-the-box, probably hiding most of our UI by triggering our deployments under the hood using the least amount of info possible (e.g. domain).

under beta release, we presume the hosting provider to have nix (and maybe be running an incus instance, see #332).

we are not planning to do a public demo, as this would involve:

given our private demo now incurs charges for deployments to non-owned domains (while our escape hatch involves editing openbao), finding a good way to avoid that so as to enable such a public demo.
open questions:
- what if multiple people want to try this simultaneously, how should that work with domains?
- do the socials have read-only modes so we can prevent people from posting?
- how would we reset the environment / keep it clean?

note that ProcoliX in a *production* setting has intended for things to work out-of-the-box, probably hiding most of our UI by triggering our deployments under the hood using the least amount of info possible (e.g. domain). under beta release, we presume the hosting provider to have nix (and maybe be running an incus instance, see #332). we are not planning to do a public demo, as this would involve: - given [our private demo](https://panel.fediversity.cfd/) now incurs charges for deployments to non-owned domains (while our escape hatch involves editing openbao), finding a good way to avoid that so as to enable such a public demo. - open questions: - what if multiple people want to try this simultaneously, how should that work with domains? - do the socials have read-only modes so we can prevent people from posting? - how would we reset the environment / keep it clean?

kiara referenced this issue

2026-10-01 13:20:32 +02:00

productization codebases published #1962

kiara added a new dependency

2026-10-01 17:26:15 +02:00

#228 [D2.3] brought into production [2027-11-01]