How juanjesusalejosillero/proyecto-integrado-asir works
Project type and purpose
• This is a “serverless” static website deployment pipeline. It uses Hugo to generate a static site from Markdown, Terraform to provision AWS infrastructure, and GitHub Actions as a GitOps-style CI/CD engine. The result is a fully automated flow: on each push to the GitHub repo, the site is rebuilt and redeployed to AWS (S3 + CloudFront), all managed as code.
File structure
• Top-level items:
• .github/workflows/workflow.yaml → GitHub Actions CI/CD definition
• Terraform/ → contains IAM, S3, CloudFront, remote‐state, variables, providers definitions
• “Blog de Juanje”/ → Hugo site source (config.toml, archetypes, content, static assets, theme submodule)
• img/ → repository images (Diagrama.png, Portada.png)
• Patterns & conventions:
• Hugo’s default layout under “Blog de Juanje” follows its content → static → themes separation
• Terraform folder uses separate .tf files for each resource group (S3, CloudFront, state backend)
README for additional insights
• It explicitly lists AWS services (IAM, ACM, S3, CloudFront, AWS CLI), Terraform, Hugo, and GitHub Actions.
• The goal: on each commit, trigger a GitHub Action that runs Terraform (apply/plan), then Hugo build, then AWS CLI sync + CloudFront invalidation.
• Infrastructure resides in us-east-1 and uses remote state locking via Terraform backend.