How atulkamble/ec2-webserver-git-setup works
This repository is a procedural guide, not an implemented deployment tool. Its principal workflow takes an operator from EC2 provisioning through web-server setup and Git-based content deployment to visiting the site; HTTPS is an optional branch. The guide also documents optional GitHub hosting and a post-receive hook. Edges reflect README-described steps only; no source excerpts were available to verify their runtime wiring.
Main entry points: README.md Post-Receive Hook
Components 12
Provisioning
- AWS Console
- EC2 Instance
README.md - SSH Session
README.md
Server Setup
- Git and Server Install
README.md - Apache or Nginx
README.md - Web Content
README.md
Git Deployment
- Web Directory Repo
README.md - GitHub Remote
- Post-Receive Hook
README.md
Site Access
- Certbot HTTPS
README.md
Other components
- Operator
- Website Visitor
Connections 16
- Operator → AWS Console: launches instance
README.md - AWS Console → EC2 Instance: provisions
README.md - Operator → SSH Session: connects by SSH
README.md - SSH Session → EC2 Instance: accesses
README.md - Operator → Git and Server Install: installs
README.md - Git and Server Install → Apache or Nginx: sets up
README.md - Operator → Web Directory Repo: initializes
README.md - Operator → Web Content: creates and commits
README.md - Web Directory Repo → Web Content: tracks
README.md - Operator → GitHub Remote: links and pushes
README.md - Operator → Post-Receive Hook: creates and enables
README.md - GitHub Remote → Post-Receive Hook: triggers deployment
README.md - Post-Receive Hook → Web Content: checks out changes
README.md - Website Visitor → Apache or Nginx: requests site
README.md - Operator → Certbot HTTPS: optionally configures
README.md - Certbot HTTPS → Apache or Nginx: secures with TLS
README.md