# Repositories & CI/CD pipeline

This application consists of one main server and one or many rendering servers. For shared types, there is an exchange library.

## Repositories

[Verfassungsbooks/Verfassungsbooks](https://github.com/Verfassungsblog/Verfassungsbooks)

[Verfassungsbooks/Verfassungsbooks-Rendering-Server](https://github.com/Verfassungsblog/Verfassungsbooks-Rendering-Server)

[Verfassungsbooks/Verfassungsbooks-Exchange-Lib](https://github.com/Verfassungsblog/Verfassungsbooks-Exchange-Lib)

## CI/CD Pipeline

Currently, we are using GitHub actions to automatically build and test on new commits or pull requests. Pushs to the `Verfassungsbooks` master branch are also automatically deployed to the [staging test environment](https://editor-staging.verfassungsblog.de), pushs to the `Verfassungsbooks-Rendering-Server` master branch are automatically deployed to the staging test rendering server (editor-staging-rendering1.verfassungsblog.de)

### GitHub Action Workflows

The repositories have three GitHub workflows configured:

- build-master.yml -> Builds and tests commits to the master branch, automatically deploys them to the staging system
- build-test-all.yml -> Builds ant tests commits / pull requests to any branch (except master)
- push-to-prod.yml -> manually triggered; builds and tests a specific commit, deploys to productive system (editor.verfassungsblog.de / editor-rendering1.verfassungsblog.de)