Skynet/nixos
7
1
Fork 0
Code Issues 45 Pull requests 1 Projects Releases Packages Wiki Activity Actions

fix: switch over to usign `active-git instead of active-gitlab`
All checks were successful
Build_Deploy / linter (push) Successful in 4s
Details
Build_Deploy / build (push) Successful in 14s
Details
Build_Deploy / deploy_dns (push) Successful in 50s
Details
Build_Deploy / deploy_active (active) (push) Successful in 1m1s
Details
Build_Deploy / deploy_active (active-core) (push) Successful in 1m16s
Details
Build_Deploy / deploy_active (active-ext) (push) Successful in 30s
Details

Browse source
This commit is contained in:
silver 2025-01-09 22:53:14 +00:00
parent 078e12cbd7
commit b46eca16b0
Signed by: silver
GPG key ID: 36F93D61BAD3FD7D
6 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -43,7 +43,7 @@ colmena build --on @active-dns
Deploying is putting (apply-ing) the config tat was built onto the server, there is no need to build first, it will automatically do so.
While the ***recommended way of deploying is using the CI/CD process*** there are times when you will have to manually deploy the config.
One such case is the ``@active-gitlab`` group if either Gitlab or Gitlab-runner got updated.
One such case is the ``@active-git`` group if either Gitlab or Gitlab-runner got updated.
Another is if ye have fecked up DNS.
Your ``~/.ssh/config`` should be set up as follows and you should be a member of ``skynet-admins-linux``
@ -60,10 +60,10 @@ Then you can run the following commands like so:
```shell
colmena apply
colmena apply --on @active-dns
colmena apply --on @active-gitlab
colmena apply --on @active-git
```
The CI/CD pipeline has a manual job that can be triggered to update ``@active-gitlab`` if you know it wont cause issues.
The CI/CD pipeline has a manual job that can be triggered to update ``@active-git`` if you know it wont cause issues.
### Agenix