ditch entity relations diagram over redundancy with data model and interactions

This commit is contained in:
Kiara Grouwstra 2025-06-05 09:06:06 +02:00
parent 4c9b2ca876
commit 0b43de1ef5
Signed by: kiara
SSH key fingerprint: SHA256:COspvLoLJ5WC5rFb9ZDe5urVCkK4LJZOsjfF4duRJFU

View file

@ -215,14 +215,10 @@ The process of migrating one's applications to a different host encompasses:
- back-up/restore scripts [using SelfHostBlocks](https://shb.skarabox.com/contracts.html)
- application-specific migration scripts, to e.g. reconfigure of connections/URLs
Relationships among the entities used to model migrations are as follows, using the crow's foot notation to denote cardinality:
![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/entity-relations.svg)
### Data model
Whereas the bulk of our configuration logic is covered in the [configuration schema](#sample-configuration-schema), our reference front-end application does in fact store data.
The design for its data model to support the desired functionality is as follows:
The design for its data model to support the desired functionality is as follows, using the crow's foot notation to denote cardinality:
![](https://git.fediversity.eu/Fediversity/meta/raw/branch/panel-data-model/architecture-docs/panel-data-model.svg)