← RETURN TO CITADEL
♜ AUTO DEPLOY PIPELINE
GIT WORKFLOW · DEPLOYMENT SCRIPTING · STATUS GENERATION · CHANGE CONTROL
STATUS: ACTIVE WORKFLOW
PROJECT OVERVIEW
The Auto Deploy Pipeline documents the Git-based workflow used to update The Citadel.
It includes source control, deployment scripting, telemetry generation, and operational
validation after changes are made.
This workflow helps turn The Citadel from a manually edited website into a more structured
systems administration and portfolio deployment process.
CURRENT WORKFLOW
Edit files
↓
Generate status.json
↓
git status
↓
git add .
↓
git commit
↓
git push origin main
↓
Validate rootandrook.com
CURRENT CAPABILITIES
- Project files are tracked through Git.
- GitHub stores the Citadel project history.
- Commit history documents infrastructure and documentation changes.
- Status telemetry is generated through Bash and exposed through status.json.
- Public site changes are validated through rootandrook.com.
COMMAND AREAS PRACTICED
git status
git add .
git commit -m "message"
git push origin main
./scripts/generate-status.sh
curl http://localhost/status.json
LESSONS LEARNED
- Git history creates a clear record of project growth.
- Deployment scripts reduce repetitive manual steps.
- Status endpoints help validate operational state after changes.
- Documentation should be committed alongside infrastructure changes.
NEXT OBJECTIVES
- Improve deployment automation and reduce manual steps.
- Document recovery steps for rebuilding The Citadel on a new VM.
- Add architecture checks before deployment.
- Explore GitHub Actions or local hooks for future automation.