Skip to content

bryanhermass/services-project

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Service Project

Status Terraform Traefik Umami Jenkins

📋 Description

Service-Project is a set of technologies for hosting and managing multiple web services. The project uses AWS as the main cloud provider and is built following infrastructure as code (IaC) best practices.

🎯 Purpose

  • Personal Services: Hosting personal projects such as web portfolio, personal blog, and development tools.
  • Client Projects: Hosting websites and applications developed for third parties.
  • Productive Tools: Deployment of useful services such as analytics, monitoring, and management tools.

🏗️ Architecture

  • Cloud Infrastructure (AWS)

    • EC2 for main services
    • Docker for containers
    • RDS for databases
    • VPC configured with public and private subnets
    • Route53 for DNS management
    • Pritunl VPN for remote access
  • Reverse Proxy (Traefik)

    • Automatic SSL certificate management
    • Microservices routing
    • Load balancing
    • Service monitoring
  • Analytics (Umami)

    • Web traffic analysis
    • User metrics
    • Conversion tracking
    • Custom reporting

🚀 Main Features

  • Service Portal

    • Web application deployment
    • Personal portfolio hosting
    • Personal tools hosting
    • Third-party project management
  • Deployed Services

    • Professional portfolios
    • Custom web applications
    • Development tools
    • Open source projects
    • Demos and prototypes
  • Technical Features

    • Automated deployment with Terraform
    • Intelligent routing with Traefik
    • Traffic analysis through Umami
    • Automatic backups

💻 Tech Stack

  • Database: PostgreSQL
  • IaC: Terraform
  • Proxy: Traefik
  • Analytics: Umami
  • Containers: Docker
  • CI/CD: Jenkins (in development)

🔄 CI/CD Pipeline (In Development)

Currently implementing a continuous integration and deployment pipeline using Jenkins, which will include:

  • Phase 1 (In Development):

    • GitHub integration
    • Automated testing
    • Static code analysis
    • Vulnerability scanning
    • Docker image building
  • Phase 2 (Planned):

    • Automated staging deployment
    • Integration testing
    • Production deployment
    • Automatic notifications

⚠️ Note: The CI/CD pipeline is currently under development and not fully operational. At present, deployments are performed manually following documented procedures.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published