How yoshihirouehara3333/timesmanager works
Project type and purpose
• This is a composite backend application consisting of:
• A SlackBot implemented as AWS Lambda functions in Node.js (under “slackbot/”)
• A Java Spring Boot REST API service (under “springboot/”)
• GitHub Actions–based CI/CD pipelines for dev and prod deployments
• Purpose: handle time-management commands from Slack users, process them in Lambda, and persist/query data via the Spring Boot API.
File structure
• Top-level directories:
• .github/workflows — GitHub Actions definitions (deploy_dev.yml, deploy_prod.yml, deploy_springboot_dev.yml)
• slackbot — Node.js Lambda source code and package.json
• springboot — Java backend API code
• Configuration/build scripts:
• package.json for Lambda dependencies and build scripts
• Maven/Gradle build files inside springboot (implied)
• Deployment manifests:
• GitHub Actions YAML files drive CI/CD for both Lambda and Spring Boot services
Key insights from the README
• Two distinct runtime environments: serverless (Lambda) and container/VM‐based (Spring Boot).
• CI/CD is handled via GitHub Actions workflows tailored for dev and prod targets.