website-and-documentation/resources/likec4/views/deployment/otc/forgejo-runner-connections.md at 286b427ed8e30b16c459fafbe6322f15de049891

Stephan Lo 286b427ed8 feat(architecture): migrate LikeC4 models from edp-doc with Git history

Port the complete LikeC4 architecture documentation from the edp-doc
repository to this repository, establishing it as the primary source
for C4 architecture models.

Migration Details:
- Migrated all C4 models from edp-doc/docs/likec4 to resources/likec4/
- Preserved Git history using git filter-branch and git read-tree
- Includes 54 C4 source files covering deployment, components, and views
- Updated LikeC4 to v1.42.1 (from deprecated v0.40.0)

Directory Structure:
- resources/likec4/models/ - C4 model definitions (components, containers, context, code)
- resources/likec4/views/ - View definitions (deployment, EDP, high-level concepts, dynamic)
- resources/likec4/deployment/ - Deployment-specific models (KIND, OTC)
- resources/likec4/doc/ - Documentation and screenshots

Architecture Coverage:
- OTC FaaS deployment architecture
- EDP component and container models
- Developer landscape and workflows
- GitOps inner/outer loop processes
- Infrastructure components (ArgoCD, Forgejo, Keycloak, Crossplane, etc.)

Dependencies:
- likec4@1.42.1
- @likec4/cli@0.40.0

This migration makes the ipceicis-developerframework repository the
authoritative source for architecture documentation. The edp-doc
repository may reference these models via git submodule if needed.

Related: Migration from https://edp.buildth.ing/DevFW/edp-doc

2025-10-24 13:08:28 +02:00

696 B

Raw Blame History

flowchart TD
    subgraph Forgejo
        forgejoActions[Forgejo Actions]
        forgejogit[ForgejoGit]
    end
    forgejoRunner[Forgejo Runner]
    imageregistry[Forgejo OCI Image Registry]

    forgejoActions -- runs workflows --> forgejoRunner
    forgejogit -- triggers on push --> forgejoRunner
    forgejoRunner -- pushes new image --> imageregistry
    forgejoRunner -- pushes new appspec --> forgejogit

This diagram shows the main components that connect to forgejo-runner:

Forgejo Actions triggers workflows to be run by the runner.
ForgejoGit triggers the runner on push events.
The runner interacts with the image registry and git as part of CI/CD flows.

696 B Raw Blame History

696 B

Raw Blame History