How ganesang/snipe-it works
This repository automates deploying Snipe-IT and MySQL on AWS: an operator configures and applies Terraform, which provisions the cloud deployment; Docker Compose runs the application services. The deployment also schedules daily MySQL backups to S3 and keeps service configuration there for use if the EC2 instance must be recreated. The graph reflects README-documented relationships only; source excerpts were not provided, so internal Terraform resource details and service-level interactions are not inferred.
Main entry points: deployment S3 bucket · docker-compose.yml Docker Compose · main.tf Backup cron job · snipeit EC2 instance
Components 10
Cloud deployment
- Terraform config
deployment - AWS resources
- EC2 instance
deployment/snipeit
Application services
- Docker Compose
src/docker-compose.yml - Snipe-IT
src/docker-compose.yml - MySQL
src/docker-compose.yml
Recovery and backups
- Backup cron job
deployment/snipeit/main.tf - S3 bucket
deployment - Service configuration
src/env.example
Other components
- Operator
Connections 8
- Operator → Terraform config: configures and applies
README.org - Terraform config → AWS resources: provisions resources
README.org - Docker Compose → Snipe-IT: runs
README.org - Docker Compose → MySQL: runs
README.org - Backup cron job → MySQL: backs up
README.org - Backup cron job → S3 bucket: stores backups
README.org - Operator → S3 bucket: uploads configuration
README.org - S3 bucket → EC2 instance: supplies configuration on recreation
README.org