ESD Project for AY22/23 Sem 2
Members: Atrayee Dutt, Bernice Teo, Bryan Lee, Ivan Yeo, Lim Xun Yi, Regine Tan
The CLUMSY application can only work when both the backend and the frontend are running
- File directory:
ESDGroup2/backend
- Command line:
docker-compose up
Docker Images | Docker Containers |
---|---|
bernicesmu/event:1.0 | event |
bernicesmu/auth | exco |
bernicesmu/upload_signup:1.0 | upload_signup-ms |
bernicesmu/attendance:1.0 | attendance |
bernicesmu/generatetoken | generatetoken |
bernicesmu/amqplistener | amqplistener-service |
bernicesmu/clumsybot | clumsybot-service |
bernicesmu/springboot-studentservice | student |
mysql:latest | telesqldb-service |
mysql:latest | mysql_db |
mysql | mysqldb |
postgres:13 | eventDb |
bernicesmu/event:1.0 | eventMigration |
- File directory:
ESDGroup2/frontend/main-app
- Command line:
npm run start
Password | |
---|---|
[email protected] | chicken123 |
[email protected] | chicken123 |
- Ensure backend has been started and Notification service is running.
- Search
@clumy_notibot
on Telegram. - Enter
/start
and follow bot's instructions. - Key in a matriculation number that is available on the frontend pages.
Please use the Excel file Sign Up Sheet.xlsx
located in ESDGroup2/frontend/main-app/src/assets
to test out the upload sign up sheet feature in the Attendance UI.
This is only applicable to services that uses volumes
in docker
to persist data through restarts.
- Ensure that the relevant containers have been deleted. Use
docker-compose down
. - Go to volume tab inside Docker Desktop and locate the relevant volumes. Delete those volumes.
- Additionally, ensure that
restart: always
is set on the service tied with the deleted volume / database. This is to prevent instances wheredocker
takes longer to initialize the db and your service is unable to connect to it.
The credentials for the AMQP and Telegram Bot set up are not included in this GitHub repository for security reasons.