How choiwoojae1547/hospital works
Project type and purpose
• From the file tree and README, this is a containerized PHP web application (“hospital”) that connects to AWS. It uses Composer for dependency management (composer.json), has a single entry point (index.php), and is deployed to AWS using Kubernetes manifests and AWS CI/CD descriptors (buildspec.yaml, aws-auth.yaml).
File structure
• Top-level code artifacts:
• Dockerfile – builds a PHP container image
• composer.json – PHP dependencies
• index.php – application entrypoint
• AWS CI/CD and infra-as-code:
• buildspec.yaml – AWS CodeBuild instructions
• aws-auth.yaml – IAM permissions for EKS
• Kubernetes deployment:
• deployment.yaml – Deployment spec for EKS
• service.yaml – Service spec (ClusterIP or LoadBalancer)
• configmap.yaml – Application configuration
• There is no dedicated “frontend” folder, so this is a back-end/monolith service container.
README for additional insights
• README simply says “hospital – connection to AWS,” confirming that the main goal is to run the hospital application in AWS.