tweak project proposal #1
1 changed files with 3 additions and 3 deletions
|
@ -141,14 +141,14 @@ The process of migrating one's applications to a different host encompasses:
|
||||||
|
|
||||||
### Data model
|
### Data model
|
||||||
|
|
||||||
Whereas the bulk of our configuration logic is covered in the configuration schema, our reference front-end application does in fact store data.
|
Whereas the bulk of our configuration logic is covered in the configuration schema, our reference front-end applications will store data.
|
||||||
The design for its data model to 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="https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/panel-data-model.svg" alt="" style="max-width:600px;"/>
|
<img src="https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/panel-data-model.svg" alt="" style="max-width:600px;"/>
|
||||||
|
|
||||||
### 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 VMs 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:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue