website-and-documentation/resources/edp-likec4/views/deployment/otc/forgejo-runner-connections.md at 3239cfbc62e8bc80b03c9570e5418fcfbcb45433

Stephan Lo 3239cfbc62 refactor(architecture): reorganize LikeC4 projects and consolidate webcomponents

Renamed resources/likec4 to resources/edp-likec4 to better reflect that this
directory contains the Enterprise Developer Platform architecture models,
not documentation platform architecture.

Extended element kinds in edp-likec4/models/spec.c4 to support documentation
platform modeling:
- Added person, tool, process, repository element kinds
- These allow modeling of documentation workflows and processes

Consolidated webcomponent generation:
- Combined both architecture projects (edp-likec4 and doc-likec4) into a
  single webcomponent output at static/js/likec4-webcomponent.js
- Updated Taskfile.yml to generate from edp-likec4 directory
- Removed duplicate webcomponent script loading in head-end.html
- Fixed CustomElementRegistry duplicate registration issue

Embedded TeleNeoOffice corporate fonts:
- Added font files to static/fonts/ and static/ root
- Required for correct rendering of diagrams in webcomponent
- Fonts are embedded in webcomponent but also served from Hugo static paths
- Fixed 404 errors for font loading

Updated architecture documentation:
- Fixed markdown linting issues (trailing spaces, fence spacing)
- Updated all references from resources/likec4 to resources/edp-likec4
- Enhanced setup.md with correct directory structure

This refactoring enables:
1. Clear separation between EDP architecture and documentation platform models
2. Single consolidated webcomponent containing all architecture views
3. Proper font loading for corporate branding in diagrams
4. Foundation for future architecture documentation expansion

Breaking changes: None (paths updated in documentation)

2025-11-07 11:50:17 +01: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