describe CI/CD #34
					 1 changed files with 5 additions and 0 deletions
				
			
		|  | @ -169,3 +169,8 @@ 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: | ||||
| 
 | ||||
|  | ||||
| 
 | ||||
| ### 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. | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue