Compare commits
No commits in common. "a227815ad6990ed287ef52462fc0bb5f8af1dd94" and "28271f8dc65b8307b6414e2cf6d368c16c7b13f3" have entirely different histories.
a227815ad6
...
28271f8dc6
21
readme.md
21
readme.md
|
@ -314,27 +314,14 @@ npm test
|
|||
|
||||
If plans go right, nixos Hydra will be used to compile packages, create docker images and also package source code in zip files.
|
||||
By default the repos (both server and clients) will have a nix flake with `hydraJobs` that describe every step on how to build it.
|
||||
If plans go south, as a backup actions will be used for this process.
|
||||
If plans gou south, as a backup actions will be used for this process.
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
A(Git push)
|
||||
A --> B(Build services)
|
||||
B --> C(Run tests)
|
||||
C --> D(Deploy to test server)
|
||||
```
|
||||
|
||||
## CD _Continuous Deployment_
|
||||
|
||||
After hydra build the packages, via actions a system configuration will be compiled and deployed onto a nixos virtual machine running on [4o1x5](https://git.4o1x5.dev/4o1x5.dev)'s nix server.
|
||||
It will we a publicly accessible developer demo for testing.
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
P[Push to dev] -->
|
||||
A[Hydra builds packages]
|
||||
A --> B[Actions issue a remote build to vm]
|
||||
B --> C[VM restarts service]
|
||||
A --> B(Build services)
|
||||
B --> C(Run tests)
|
||||
C --> D(Deploy to test server)
|
||||
```
|
||||
|
||||
## Git _Version control_
|
||||
|
|
Reference in a new issue