sig_core/wiki
7
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Activity

clarity to sop
All checks were successful
mkdocs build / build (push) Successful in 28s
Details

Browse Source
This commit is contained in:
Louis Abel 2024-12-13 19:48:26 -07:00
parent 6632356224
commit a62e27b9b0
Signed by: label
GPG Key ID: 2A6975660E424560
2 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sop/sop_compose.md
View File

@ -133,8 +133,10 @@ Once the syncs are done, staging must be tested and vetted before being sent to
``` ```
# Set X to whatever release # Set X to whatever release
bash RLVER=X sync-to-prod.delete.sh RLVER=X bash sync-to-prod.delete.sh
bash sync-file-list-parallel.sh bash sync-file-list-parallel.sh
# Sends data to the vault and masks repodata
RLVER=X bash vault-release-no-repodata.sh
``` ```
During this phase, staging is rsynced with production, the file list is updated, and the full time list is also updated to allow mirrors to know that the repositories have been updated and that they can sync. During this phase, staging is rsynced with production, the file list is updated, and the full time list is also updated to allow mirrors to know that the repositories have been updated and that they can sync.

24
docs/sop/sop_compose_8.md
View File

@ -42,6 +42,17 @@ There is a designated system that takes care of composing repositories. These sy
Each repository or set of repositories are controlled by various pungi configurations. For example, `r8.conf` will control the absolute base of Rocky Linux 8, which imports other git repository data as well as accompanying json or other configuration files. Each repository or set of repositories are controlled by various pungi configurations. For example, `r8.conf` will control the absolute base of Rocky Linux 8, which imports other git repository data as well as accompanying json or other configuration files.
### Quick Compose
On the designated compose box, there is a script that can do all of the incremental steps.
```
cd /root/cron
bash stable-updates
```
After, it can be synced to production.
### Running a Compose ### Running a Compose
Inside the `pungi` git repository, the folder `scripts` contain the necessary scripts that are ran to perform a compose. There are different types of composes: Inside the `pungi` git repository, the folder `scripts` contain the necessary scripts that are ran to perform a compose. There are different types of composes:
@ -135,17 +146,4 @@ During this phase, staging is rsynced with production, the file list is updated,
**Note**: If multiple releases are being updated, it is important to run the syncs to completion before running the file list parallel script. **Note**: If multiple releases are being updated, it is important to run the syncs to completion before running the file list parallel script.
## Quicker Composes
On the designated compose box, there is a script that can do all of the incremental steps.
```
cd /root/cron
bash stable-updates
```
The same goes for a full production.
```
bash stable
```