Fediversity/meta
13
3
Fork 4
Code Issues Pull requests Projects Releases Packages Wiki Activity

set graph width for print documents

Browse source 
Signed-off-by: cinereal <cinereal@riseup.net>
This commit is contained in:
Kiara Grouwstra 2025-09-09 12:38:58 +02:00
parent 4820b0dacf
commit 6ecf75b76e
Signed by: kiara
SSH key fingerprint: SHA256:COspvLoLJ5WC5rFb9ZDe5urVCkK4LJZOsjfF4duRJFU
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
architecture-docs/architecture.md
View file

@ -131,7 +131,7 @@ The used legend is as follows:
For further info on components see the [glossary](#glossary). For further info on components see the [glossary](#glossary).
<!-- ![](./interactions-migration.svg) --> <!-- ![](./interactions-migration.svg) -->
![](./interactions-migration.png) ![](./interactions-migration.png){ width=100% }
### Configuration data flow ### Configuration data flow
@ -144,7 +144,7 @@ For its runtime setup, a hosting provider has to supply a **resource mapping** t
Applications and runtime environments thus interface through **resources**, the properties of which are curated by Fediversity maintainers. Applications and runtime environments thus interface through **resources**, the properties of which are curated by Fediversity maintainers.
<!-- ![](./interactions-fediversity.svg) --> <!-- ![](./interactions-fediversity.svg) -->
![](./interactions-fediversity.png) ![](./interactions-fediversity.png){ width=100% }
### Service portability ### Service portability
@ -162,13 +162,14 @@ The process of migrating one's applications to a different host encompasses:
Whereas the bulk of our configuration logic is covered in the configuration schema, [implemented here](https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/deployment/data-model.nix) and [tested here](https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/deployment/data-model-test.nix), our reference front-end applications will store data. Whereas the bulk of our configuration logic is covered in the configuration schema, [implemented here](https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/deployment/data-model.nix) and [tested here](https://git.fediversity.eu/Fediversity/Fediversity/src/branch/main/deployment/data-model-test.nix), our reference front-end applications will store data.
The data model design for the configuration front-end needed support the desired functionality is as follows, using the crow's foot notation to denote cardinality: The data model design for the configuration front-end needed support the desired functionality is as follows, using the crow's foot notation to denote cardinality:
<img src="./panel-data-model.svg" alt="" style="max-width:600px;"/> <!-- ![](./panel-data-model.svg) -->
![](./panel-data-model.png){ height=100% }
### Host architecture ### Host architecture
Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support as part of our exploitation would be as follows, where virtual machines in question run Fediversity to offer our selected applications: Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support as part of our exploitation would be as follows, where virtual machines in question run Fediversity to offer our selected applications:
![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png) ![](./host-architecture.png){ width=100% }
### CI / CD ### CI / CD