Stephan Lo
286b427ed8
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 |
||
|---|---|---|
| .devcontainer | ||
| .github/workflows | ||
| .vscode | ||
| assets | ||
| content/en | ||
| layouts | ||
| resources | ||
| scripts | ||
| .dockerignore | ||
| .env.versions | ||
| .gitignore | ||
| .gitmodules | ||
| .htmltest.yml | ||
| .htmlvalidate.json | ||
| .markdownlint.json | ||
| config.yaml | ||
| devbox.json | ||
| devbox.lock | ||
| DOCKER.md | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| hugo.toml | ||
| package-lock.json | ||
| package.json | ||
| README-developer.md | ||
| README.md | ||
| RELEASE.md | ||
| Taskfile.yml | ||
| TESTING.md | ||
| VERSIONS.md | ||
IPCEICIS-DeveloperFramework Documentation
This repo contains business and architectural design and documentation of the DeveloperFramework subproject of IPCEI-CIS.
How to read and contribute to this documentation locally
The documentation is done in Hugo-format.
Hugo is a static site renderer - so to get the documentation site presented you need a running Hugo processor. Therefore there is
- either a Hugo
.devcontainer-definition - just run a devcontainer aware IDE or CLI, e.g. Visual Studio code - or a Hugo
Devbox-definition - in this case just run a devbox shell
Local installation of the Hugo documentation system
We describe two possible ways (one with devcontainer, one with devbox) to get the Hugo-documentation system locally running.
For both prepare the following three steps:
- open a terminal on your local box
- clone this repo:
git clone https://forgejo.edf-bootstrap.cx.fg1.ffm.osc.live/DevFW/website-and-documentation - change to the repo working dir:
cd website-and-documentation
Possibility 1: Hugo in a devcontainer
devcontainers are running containers as virtual systems on your local box. The defintion is in the .devcontainer folder.
Thus as preliminary you need a container daemon running, e.g. Docker.
There are several options to create and run the devcontainer - we present here two:
Option 1: Run the container triggered by and connected to an IDE, e.g. VS Code
- open the repo in an Devcontainer-aware tool/IDE (e.g.
code .) - start the
devcontainer(in VSC it'sF1 + Reopen in Devcontainer) - when the container is up & running just open your browser with
http://localhost:1313/
Option 2: Run the container natively
An alternative to get the container image is the devcontainer CLI, then you can run the devcontainer without VS Code. Thus as preliminary you need to do the install steps of the devconatiner cli.
- start the devcontainer by running:
devcontainer up --workspace-folder . - find out the IP address of the devconatiner by using
docker psanddocker inspect <id of container> - when the container is up & running just open your browser with
http://<DOCKER IP>:1313/
Possibility 2: Hugo in a devbox
Devboxes are locally isolated environments, managed by the Nix package manager. So first prepare the devbox.
Then
devbox shell- In the shell:
hugo serve
Editing
Documentation language
The documentation is done in Docsy-Theme.
So for editing content just goto the content-folder and edit content arrording to the Docsy documentation
Commiting
After having finished a unit of work commit and push.
Annex
Installation steps illustrated
When you run the above installation, the outputs could typically look like this:
In Visual Studio Code
Reopen in Container
Hugo server is running and (typically) listens to localhost:1313
After some installation time you have:
Final result in a web browser
