How mmorejon/erase-una-vez-1 works
Main Components
• Application Code: Represented by main.go and managed by Go modules (go.mod). This is the core logic that prints the message.
• CI/CD Pipeline: The presence of the .github/workflows folder and the release.yaml file suggests the project uses GitHub Actions for building, testing, or releasing the app. Include a CI/CD component indicating automated builds/deployments.
• Configuration & Deployment: The manifests.yaml file (and any Kubernetes-related configuration hinted by the book reference “Érase una vez Kubernetes”) can be shown as a deployment descriptor for Kubernetes, denoting integration with container orchestration.
Relationships and Interactions
• Environment Variables: The README describes how variables like SLEEP_TIME and CHARACTER modify the app’s behavior at runtime. Illustrate this as a configuration interface into the containerized application.
• CI/CD Pipeline: Illustrate how code changes (pushed to the repository) trigger workflows in GitHub Actions, which in turn build a Docker image and push it to a container registry.
• Deployment Artifact: If applicable, include a connection from the CI/CD pipeline to your deployment infrastructure (e.g., a Kubernetes cluster as hinted by manifests.yaml), indicating where the Docker container might be deployed.
Architectural Patterns and Design Principles
• Containerization: Emphasize the use of Docker to isolate and run the application.
• Source Code Management and Automation: Show how GitHub Actions facilitate continuous integration and continuous deployment.
• Configuration via Environment Variables: Note that the design follows the principle of externalizing configuration for ease of modification and deployment flexibility.
Relevant Technologies
• Golang (Go): The programming language in which the application is written.
• Docker: For containerizing the application.
• GitHub Actions: For the CI/CD processes.