website-and-documentation/resources/edp-likec4/deployment/otc/edp.c4
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

49 lines
No EOL
1.4 KiB
Text

// Deployment model
deployment {
cloud otc-edp-per-tenant 'OTC EDP per tenant cluster' {
description 'OTC environment for EDP. EDP is the environment a customer gets from us.
This is kubernetes clusters and other infrastructure like nodes and vms, and platform services. All is set up by IaC-pipelines in the Foundry.
'
technology 'OTC'
kubernetes cce 'OTC CCE' {
description 'OTC Container Cluster Engine'
icon tech:kubernetes
technology 'Kubernetes'
cluster edp 'EDP' {
instanceOf edp.argoCD
instanceOf forgejoRunner
instanceOf edp.forgejo {
-> cloudServices.elasticsearch
-> cloudServices.objectstorage
-> cloudServices.postgres
-> cloudServices.redis
}
instanceOf edp.externalSecrets
instanceOf edp.ingressNginx
}
}
paas cloudServices 'EDP Cloud Services' {
description 'EDP Cloud Services'
technology 'Cloud Services'
instanceOf postgres
instanceOf redis
instanceOf objectstorage
instanceOf elasticsearch
}
computeressource forgejoRunnerInfrastructure 'EDP ForgejoRunner infrastructure' {
description 'Infrastructure for Forgejo runners like pods, vms, lxds, etc'
instanceOf forgejoRunner {
-> cce.edp.forgejo 'registers'
}
}
}
}