How msoares94/i-educar-ansible-playbook works
Project Type and Purpose
• This is an Infrastructure-as-Code (IaC) / configuration-management project written in Ansible.
• Its goal: fully automate installation and configuration of the i-Educar application (PHP/Nginx/PostgreSQL/Redis) across multiple environments (development, staging, production).
High-Level Architecture Components
A. Control Plane (Ansible Machine)
• Inventory & Hosts Definition
– inventory.ini (with host groups: [ieducar])
• Environment Variables
– group_vars/all/*.yml (global vars)
– group_vars/{development,staging,production}/main.yml
• Playbooks & Tasks
– playbook.yml (main orchestration)
– add-key.yml (SSH key bootstrap)
• Roles Directory
– roles/common
– roles/postgresql
– roles/redis-server
– roles/php-fpm
– roles/nginx
– roles/i-educar
– roles/i-educar-reports-package
– roles/i-educar-educacenso-package
B. Data Plane (Managed Servers)
• Ubuntu Server 22.04+ hosts in group [ieducar]
• On each host the playbook will install/configure:
– PostgreSQL (DB server)
– Redis (cache/session store)
– PHP-FPM (runtime for PHP app)
– NGINX (web server + reverse proxy)
– i-Educar application code & community packages
– SSL certificates (Let’s Encrypt via Certbot or provided certs)
– File permissions (ACLs)
Component Interactions & Data Flows
• Control Plane → Managed Nodes:
1) Ansible connects via SSH (inventory.ini / add-key.yml).
2) Loads group_vars based on target label (dev/staging/prod).
3) Executes playbook.yml → invokes roles in order:
common → postgresql → redis-server → php-fpm → nginx → i-educar → community packages
4) Each role runs tasks (create users, install packages, render templates, restart services).
• Within Managed Node:
• NGINX routes HTTP(S) → PHP-FPM
• PHP-FPM executes i-Educar code → interacts with PostgreSQL + Redis
• Certbot requests/renews SSL from Let’s Encrypt (if enabled)
• Templates (Jinja2) generate NGINX configs based on variables (domain, SSL flags)
Architectural Patterns & Principles
• Idempotent, role-based configuration management
• Environment-specific overrides via group_vars
• Modular roles each handling one concern (e.g., DB, cache, web, app)
• Handler notifications to restart/reload services only when needed
• Separation of concerns: network (SSH), orchestration (Ansible), provisioning (roles), application layer (i-Educar)