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

Compare commits

base: fediversity:27d621de667947b1b7073485b621d920cc17f777
Branches Tags
fediversity:main
fediversity:proposal-gantt
fediversity:interactions-maintainers
fediversity:panel-data-model
..
compare: fediversity:e5e608f2c9e026ea2f5eddf833b009d73db4c18b
Branches Tags
fediversity:main
fediversity:proposal-gantt
fediversity:interactions-maintainers
fediversity:panel-data-model

No commits in common. "27d621de667947b1b7073485b621d920cc17f777" and "e5e608f2c9e026ea2f5eddf833b009d73db4c18b" have entirely different histories.
27d621de66 ... e5e608f2c9

1 changed files with 0 additions and 5 deletions
Show stats Expand all files Collapse all files

5
architecture-docs/architecture.md
View file

@ -169,8 +169,3 @@ The data model design for the configuration front-end needed support the desired
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) ![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png)
### CI / CD
In our simplest set-up, continuous integration and continuous deployment pipelines are handled using Forgejo's [built-in runner](https://code.forgejo.org/forgejo/runner), with relevant secrets handled using [Forgejo secrets](https://forgejo.org/docs/latest/developer/secrets/). Jobs we handle using CI include linting, formatting, testing, and a periodic life-cycle management job to keep our dependencies up-to-date.
In a future iteration, we may make use of [Gerrit](https://gerrit.googlesource.com/) to better manage our review process for incoming merge requests.