fediversity/fediversity

Fork 9

kick-started initial feedback cycle #225

New issue

Open

opened 2025-03-03 16:36:22 +01:00 by kiara · 4 comments

kiara commented

2025-03-03 16:36:22 +01:00

Owner

As a host,
I want to start using Fediversity internally,
so that we may kick-start a feedback cycle toward product improvement.

Owner: Fediversity development team (following #327)

dependencies

#433 deployment provisions host infra
#313 ProxmoX back-end supports multiple users
#116 Proxmox resources are provisioned to deploy services to
#848 hosting provider may configure host environment
#142 Users can configure their desired sub-domains in the online panel, so that the deployed services are assigned the desired sub-domains
#178 provision admin accounts for deployed services
#158 users can update their deployment configurations
#185 use deployed immutable buckets
#115 Databases are provisioned so that services can use a central storage
#138 VMs use central file storage
#200 reproduce DNS machine
#117 SMTP service is provisioned so that applications can send emails
#370 fediversity apps reused in infra
#314 ephemeral state is automatically provisioned
#136 panel staging/production configuration

**As** a host, **I want** to start using Fediversity internally, **so that** we may kick-start a feedback cycle toward product improvement. **Owner**: Fediversity development team (following #327) ### dependencies 1. #433 deployment provisions host infra 1. #313 ProxmoX back-end supports multiple users 1. #116 Proxmox resources are provisioned to deploy services to 1. #848 hosting provider may configure host environment 1. #142 Users can configure their desired sub-domains in the online panel, so that the deployed services are assigned the desired sub-domains 1. #178 provision admin accounts for deployed services 1. #158 users can update their deployment configurations 1. #185 use deployed immutable buckets 1. #115 Databases are provisioned so that services can use a central storage 1. #138 VMs use central file storage 1. #200 reproduce DNS machine 1. #117 SMTP service is provisioned so that applications can send emails 1. #370 fediversity apps reused in infra 1. #314 ephemeral state is automatically provisioned 1. #136 panel staging/production configuration

kiara added a new dependency

2025-04-01 23:02:31 +02:00

#138 VMs use central file storage

kiara added a new dependency

2025-04-01 23:02:38 +02:00

#200 reproduce DNS VM

kiara added a new dependency

2025-04-01 23:02:43 +02:00

#178 admin accounts provisioned for deployed services

kiara added a new dependency

2025-04-02 08:45:31 +02:00

#136 panel staging/production configuration

kiara added a new dependency

2025-04-02 08:47:50 +02:00

#117 SMTP service is provisioned so that applications can send emails

kiara added a new dependency

2025-04-02 08:47:59 +02:00

#185 use immutable buckets from VMs

kiara added a new dependency

2025-04-02 08:48:07 +02:00

#182 use shared storage from VMs

kiara added a new dependency

2025-04-02 08:48:16 +02:00

#116 hypervisor resources are provisioned to deploy services to

kiara added a new dependency

2025-04-02 08:48:25 +02:00

#109 Have a way to make requests to the DNS service so that subdomains can be pointed to the right IP

kiara added a new dependency

2025-04-02 08:48:37 +02:00

#142 Users can configure their desired sub-domains in the online panel, so that the deployed services are assigned the desired sub-domains

kiara added a new dependency

2025-04-02 08:48:44 +02:00

#115 Databases are provisioned so that services can use a central storage

kiara added a new dependency

2025-04-02 08:51:31 +02:00

#296 orchestrator features

kiara added a new dependency

2025-04-02 16:26:03 +02:00

#298 OKR

kiara added a new dependency

2025-04-02 16:41:13 +02:00

#158 users can update their deployment configurations

kiara added this to the Fediversity project

2025-04-18 11:01:48 +02:00

kiara added a new dependency

2025-04-19 13:10:05 +02:00

#313 back-end supports multiple users

kiara added a new dependency

2025-04-28 12:34:04 +02:00

#318 peertube update breaks test services/tests/peertube.nix

kiara added the

type: key result

label

2025-05-01 12:09:03 +02:00

kiara changed title from ~~OKR: dogfooding~~ to dogfooding

2025-05-01 12:09:10 +02:00

kiara added a new dependency

2025-05-10 11:16:08 +02:00

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

kiara added a new dependency

2025-05-15 20:14:37 +02:00

#334 API specification published

kiara added a new dependency

2025-06-01 10:17:27 +02:00

#349 exploit our work by enabling reproducible deployments of an initial set of portable applications

kiara removed a dependency

2025-06-01 10:33:42 +02:00

#298 OKR

kiara changed title from ~~dogfooding~~ to kick-start initial feedback cycle

2025-06-01 12:02:19 +02:00

kiara changed title from ~~kick-start initial feedback cycle~~ to kick-started initial feedback cycle

2025-06-01 12:49:37 +02:00

kiara referenced this issue

2025-06-01 16:10:33 +02:00

initial focus on single application for development #327

kiara removed a dependency

2025-06-02 16:25:06 +02:00

#334 API specification published

kiara added a new dependency

2025-06-03 14:24:45 +02:00

#314 ephemeral state is automatically provisioned

kiara added a new dependency

2025-06-05 10:40:29 +02:00

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

kiara removed a dependency

2025-06-09 18:17:06 +02:00

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

kiara referenced this issue

2025-06-09 18:38:16 +02:00

fediversity apps reused in infra #370

kiara added a new dependency

2025-06-09 18:38:40 +02:00

#370 fediversity apps reused in infra

kiara removed this from the Fediversity project

2025-06-10 19:07:20 +02:00

kiara referenced this issue

2025-06-10 19:43:11 +02:00

exploit our work by enabling reproducible deployments of an initial set of portable applications #349

kiara removed a dependency

2025-06-16 12:00:31 +02:00

#349 exploit our work by enabling reproducible deployments of an initial set of portable applications

kiara added a new dependency

2025-07-04 12:11:02 +02:00

#433 deployment provisions host infra

kiara added

type: user story

and removed

type: key result

labels

2025-12-11 15:09:54 +01:00

kiara referenced this issue from fediversity/meta

2026-01-27 17:59:10 +01:00

add hosting provider project proposal academic freedom #35

kiara added a new dependency

2026-04-25 13:07:31 +02:00

#848 hosting provider may configure host environment

toonn commented

2026-05-11 17:04:26 +02:00

Member

#370 is closed but we don't yet use Fediversity to deploy any infra. Should we drop that dependency entirely or re-open and update its wording?

The Forgejo seems particularly risky to deploy through Fediversity because there's circularity there. If we introduce a bug the Forgejo deployment may fail in a subtle way (outright failure to deploy would not necessarily be a big deal), preventing us from pushing a fix to the repository to redo the deployment.

Since we already use both Matrix and Signal for project communication, that seems like a good candidate usecase. If a deployment goes awry we can fall back to the pre-existing communication channels.

#370 is closed but we don't yet use Fediversity to deploy any infra. Should we drop that dependency entirely or re-open and update its wording? The Forgejo seems particularly risky to deploy through Fediversity because there's circularity there. If we introduce a bug the Forgejo deployment may fail in a subtle way (outright failure to deploy would not necessarily be a big deal), preventing us from pushing a fix to the repository to redo the deployment. Since we already use both Matrix and Signal for project communication, that seems like a good candidate usecase. If a deployment goes awry we can fall back to the pre-existing communication channels.

Toast commented

2026-05-11 18:22:12 +02:00

Member

We could implement basic forgejo functionality tests like we do for our operator apps, and I think that would help with broken changes blocking us from pushing a fix for said changes

~~kiara referenced this issue 2026-05-11 18:38:12 +02:00~~

fediversity apps reused in infra #370

kiara commented

2026-05-11 18:39:27 +02:00

Author

Owner

@toonn:

fair point. fwiw, current CD jobs reuse our deployment methods, reflecting the comment in the OP here:

note that whereas operator application configuration might not apply here, reuse of our deployment methods does make sense. if we start making use of the contracts RFC, that could help here too.

as to infra-like deployment of applications in category operator, we should be able to do that today, with commands similar to those used in CD today (may be listed by nix flake show) and configuration handled thru HOSTING_ENV_CONFIG.

(as noted in the OP, we today still retain that distinction between our application categories, but i imagine having such infra categories all use our resource/configuration abstractions aimed at the operator-host divide would feel more satisfying once our resources offer more useful abstractions than they do today, e.g. using the aforementioned contracts. until then, i fear they would mostly add more boilerplate there for this use-case for now.)

for what it's worth, dogfooding infra would be nicer after #123.

@toonn: fair point. fwiw, current [CD jobs](https://git.fediversity.eu/fediversity/fediversity/actions/runs/35860/jobs/0/attempt/1) reuse our deployment methods, reflecting the comment in the OP here: > note that whereas operator application configuration might not apply here, reuse of our deployment methods does make sense. if we start making use of the contracts RFC, that could help here too. as to infra-like deployment of applications in category `operator`, we should be able to do that today, with commands similar to those used in CD today (may be listed by `nix flake show`) and configuration handled thru `HOSTING_ENV_CONFIG`. (as noted in the OP, we today still retain that distinction between our application categories, but i imagine having such infra categories all use our resource/configuration abstractions aimed at the operator-host divide would feel more satisfying once our `resource`s offer more useful abstractions than they do today, e.g. using the aforementioned contracts. until then, i fear they would mostly add more boilerplate there for this use-case for now.) for what it's worth, dogfooding infra would be nicer after #123.

kiara commented

2026-05-11 18:44:31 +02:00

Author

Owner

as some historical context, while previously this ticket had been scoped to an internal pilot with the hosting provider, i later rescoped it to be closer to dogfooding deployments for our project's own deployment needs, with #228 as a follow-up involving the hosting provider's actual clients.

toonn referenced this issue from fediversity/meta

2026-05-11 19:51:35 +02:00

add hosting provider project proposal academic freedom #35

kiara referenced this issue

2026-06-05 22:13:03 +02:00

groups each use applications, spiffe resource #1043