Commit initial : blog Docusaurus avec i18n (FR/EN)
This commit is contained in:
commit
f6e32464d9
27 changed files with 18900 additions and 0 deletions
18
i18n/en/docusaurus-plugin-content-docs/current.json
Normal file
18
i18n/en/docusaurus-plugin-content-docs/current.json
Normal file
|
|
@ -0,0 +1,18 @@
|
|||
{
|
||||
"version.label": {
|
||||
"message": "Next",
|
||||
"description": "The label for version current"
|
||||
},
|
||||
"sidebar.tutorialSidebar.category.Notions": {
|
||||
"message": "Concepts",
|
||||
"description": "The label for category Notions in sidebar tutorialSidebar"
|
||||
},
|
||||
"sidebar.tutorialSidebar.category.Homelab actuel - Docker Compose & Ansible": {
|
||||
"message": "Current Homelab - Docker Compose & Ansible",
|
||||
"description": "The label for category Homelab actuel in sidebar tutorialSidebar"
|
||||
},
|
||||
"sidebar.tutorialSidebar.category.Futur Homelab - OpenTofu, K3S, Ansible & DevOps": {
|
||||
"message": "Future Homelab - OpenTofu, K3S, Ansible & DevOps",
|
||||
"description": "The label for category Futur Homelab in sidebar tutorialSidebar"
|
||||
}
|
||||
}
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Current Homelab - Docker Compose & Ansible
|
||||
|
||||
Documentation of my current homelab infrastructure, based on Docker Compose and Ansible.
|
||||
|
||||
## Overview
|
||||
|
||||
My current homelab uses a simple and effective approach:
|
||||
- **Docker Compose**: Container orchestration
|
||||
- **Ansible**: Configuration and deployment automation
|
||||
- **Self-hosted services**: Forgejo, monitoring, various applications
|
||||
|
||||
## Architecture
|
||||
|
||||
### Physical/Virtual Infrastructure
|
||||
- Dedicated servers or VMs
|
||||
- Secure local network
|
||||
- Storage and backups
|
||||
|
||||
### Tech Stack
|
||||
- **OS**: Linux (Debian/Ubuntu)
|
||||
- **Containerization**: Docker & Docker Compose
|
||||
- **Automation**: Ansible playbooks
|
||||
- **Reverse proxy**: Traefik or Nginx
|
||||
- **Monitoring**: Prometheus, Grafana
|
||||
|
||||
## Deployed Services
|
||||
|
||||
The documentation details:
|
||||
- Service configuration
|
||||
- Ansible playbooks used
|
||||
- Docker Compose files
|
||||
- Secrets and security management
|
||||
- Backups and disaster recovery
|
||||
|
||||
## Advantages of This Approach
|
||||
|
||||
Simple to set up and maintain
|
||||
Ansible enables complete automation
|
||||
Docker Compose facilitates service management
|
||||
Reproducible and versioned with Git
|
||||
|
||||
## Limitations
|
||||
|
||||
Limited scalability
|
||||
No native high availability
|
||||
Manual orchestration for certain tasks
|
||||
|
||||
These limitations motivate the evolution towards Kubernetes (see "Future Homelab" section).
|
||||
|
|
@ -0,0 +1,72 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Future Homelab - OpenTofu, K3S, Ansible & DevOps
|
||||
|
||||
Documentation of the migration to a modern infrastructure based on Kubernetes and DevOps practices.
|
||||
|
||||
## Vision
|
||||
|
||||
Evolve my homelab towards an infrastructure that is:
|
||||
- **Cloud-native** with Kubernetes (K3S)
|
||||
- **Infrastructure as Code** with OpenTofu
|
||||
- **Highly automated** with Ansible and GitOps
|
||||
- **Observable** with advanced monitoring and logging
|
||||
|
||||
## Target Tech Stack
|
||||
|
||||
### Orchestration
|
||||
- **K3S**: Lightweight and performant Kubernetes distribution
|
||||
- **Helm**: Package manager for Kubernetes
|
||||
- **ArgoCD**: GitOps for continuous deployment
|
||||
|
||||
### Infrastructure as Code
|
||||
- **OpenTofu**: Open-source fork of Terraform for IaC
|
||||
- **Ansible**: Configuration management and provisioning
|
||||
- **Git**: Version control for all infrastructure
|
||||
|
||||
### DevOps & CI/CD
|
||||
- **Forgejo Actions**: Integrated CI/CD
|
||||
- **GitOps**: Declarative and versioned deployment
|
||||
- **Kustomize**: Kubernetes configuration management
|
||||
|
||||
### Observability
|
||||
- **Prometheus**: Metrics and alerting
|
||||
- **Grafana**: Visualization and dashboards
|
||||
- **Loki**: Log aggregation
|
||||
- **Tempo**: Distributed tracing
|
||||
|
||||
## Migration Goals
|
||||
|
||||
### Technical
|
||||
- Horizontal scalability
|
||||
- High availability
|
||||
- Automated deployments
|
||||
- Complete observability
|
||||
|
||||
### Learning
|
||||
- Master Kubernetes in production
|
||||
- Practice Infrastructure as Code
|
||||
- Implement DevOps best practices
|
||||
- Explore cloud-native technologies
|
||||
|
||||
## Roadmap
|
||||
|
||||
The migration happens in stages:
|
||||
|
||||
1. **Phase 1**: Basic K3S setup
|
||||
2. **Phase 2**: Migration of critical services
|
||||
3. **Phase 3**: GitOps implementation (ArgoCD)
|
||||
4. **Phase 4**: Observability and monitoring
|
||||
5. **Phase 5**: Complete automation with OpenTofu
|
||||
|
||||
Each step is documented with encountered challenges and solutions provided.
|
||||
|
||||
## Why This Evolution?
|
||||
|
||||
This migration represents:
|
||||
- **Professional skills**: Technologies used in enterprise
|
||||
- **Practical learning**: Experimentation in real conditions
|
||||
- **Technical evolution**: Moving to modern and scalable solutions
|
||||
- **Portfolio**: Demonstration of advanced DevOps skills
|
||||
32
i18n/en/docusaurus-plugin-content-docs/current/intro.md
Normal file
32
i18n/en/docusaurus-plugin-content-docs/current/intro.md
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Introduction
|
||||
|
||||
Welcome to **TellServ Tech Blog**!
|
||||
|
||||
This technical blog documents my research, thoughts and solutions to technical challenges encountered in my projects. The goal is to:
|
||||
|
||||
- 📚 **Document** my learnings and discoveries
|
||||
- 🔍 **Share** my analyses and solutions
|
||||
- 💡 **Demonstrate** my technical skills
|
||||
- 🤝 **Contribute** to the community
|
||||
|
||||
## Site Structure
|
||||
|
||||
### Documentation
|
||||
|
||||
The documentation section contains in-depth technical guides, tutorials and references for my projects.
|
||||
|
||||
### Blog
|
||||
|
||||
The blog features articles on:
|
||||
- Technical problem solving
|
||||
- Architecture analysis
|
||||
- Experience feedback
|
||||
- New technologies and tools
|
||||
|
||||
## About
|
||||
|
||||
This site is built with [Docusaurus](https://docusaurus.io/), hosted on Cloudflare Pages and the source code is available on [GitHub](https://github.com/Tellsanguis/blog_technique) and [Forgejo](https://forgejo.tellserv.fr).
|
||||
|
|
@ -0,0 +1,40 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Concepts
|
||||
|
||||
This section groups fundamental technical concepts and notions used in my projects.
|
||||
|
||||
## Objective
|
||||
|
||||
Document and explain key concepts to:
|
||||
- Facilitate understanding of technical choices
|
||||
- Serve as reference for projects
|
||||
- Share theoretical and practical knowledge
|
||||
|
||||
## Topics Covered
|
||||
|
||||
Covered concepts include:
|
||||
|
||||
### Infrastructure
|
||||
- Virtualization and containerization
|
||||
- Networking and security
|
||||
- Storage and backup
|
||||
|
||||
### Automation
|
||||
- Infrastructure as Code (IaC)
|
||||
- Configuration Management
|
||||
- CI/CD and pipelines
|
||||
|
||||
### DevOps
|
||||
- GitOps and versioning
|
||||
- Observability (monitoring, logging, tracing)
|
||||
- Practices and methodologies
|
||||
|
||||
### Orchestration
|
||||
- Kubernetes and containers
|
||||
- Service mesh
|
||||
- Load balancing and scaling
|
||||
|
||||
Explore the subsections to discover each concept in detail!
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# About Me
|
||||
|
||||
Coming soon.
|
||||
Loading…
Add table
Add a link
Reference in a new issue