docs: add how-to guide for private Forge dependencies in CI/CD #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ses/docs-private-libraries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We must improve new howto guides
@ -0,0 +7,4 @@## Voraussetzungen- Grundverständnis von CI/CD-Pipelines auf sebaTEC ForgeReference to the tutorial so that we make it explicit
@ -0,0 +8,4 @@## Voraussetzungen- Grundverständnis von CI/CD-Pipelines auf sebaTEC Forge- Private Abhängigkeiten (Go-Module, Hugo-Module, Python-Pakete) in sebaTEC Forge-RepositoriesRephrase sentence so that readers understand private. It means visibility within forgejo. Repos are public or private. Users/orgs do also have different visibilities. Reference to forgejo doc is helpful.
@ -0,0 +60,4 @@Lade den privaten Schlüssel als Secret hoch, damit die Pipeline ihn verwenden kann:### API-Token erstellenUse the UI approach like in other places. Reference to dedicated how-to where we explain this script/ api solution
@ -0,0 +146,4 @@# In deiner go.modrequire forge.sebatec.eu/<dein-benutzername>/private-module v1.0.0# Die Git-Konfiguration url.*insteadOf reicht aus - keine zusätzlichen Umgebungsvariablen nötigThis needs validation. We need a quick and dirty example somewhere else.
@ -0,0 +220,4 @@#### Python-Pakete```bashUse pyproject.yaml and uv.