[ARCHIVED] The backend of a ticketing program that simulates a virtual queue.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
Go to file
ALI Hamza 28fbf77529
continuous-integration/drone/push Build is passing Details
ib: Add boilerplate for criterion b
2019-09-23 20:28:37 +07:00
.drone.yml ci: Cache Go Dependencies 2019-09-05 11:09:54 +07:00
.gitignore IB: Add Crit A in planning.md 2019-09-19 07:02:07 +07:00
README.md Add DroneCI badge 2019-09-05 10:36:08 +07:00
go.mod Drone integration and Go module setup 2019-09-05 08:54:21 +07:00
main.go Drone integration and Go module setup 2019-09-05 08:54:21 +07:00
planning.md ib: Add boilerplate for criterion b 2019-09-23 20:28:37 +07:00
recordtasks.md ib: Add boilerplate for criterion b 2019-09-23 20:28:37 +07:00

README.md

Build Status

JIS Queueing System

Go project for Web backend for a whole family of projects with similar ideas

As a relatively large school, we have many visitors who come visiting and need to talk to the administrators. This project is created as a way to make it easier for visitors to queue up for whomever the need to see, with the least of hassle. This queueing system is planned to support multiple branches (multiple queues), sends information regarding queueing via web sockets to keep it updated. Frontend will most be written in ReactJS.

How will the system work

Here is a little example of the end goal of this project:
  1. Visitor enters the school premise.
  2. Visitor selects which branch queue to join (School visit, speak to school admins, etc..).
  3. Visitor Enters name and email, {TBA}, and queue number.
  4. Visitor gets email notification thanking them for coming.
  5. Visitor waits for queue number to be called.
  6. Visitor goes where they would like to.

Other information

  • The devices which connected to the system at once;
    • One for where visitors sign up.
    • One for displaying current queues and each queue status.
    • n computers that are all ready to 'accept' visitors for each specific branch.
  • Websockets will live update the queue display.
  • When a branch user clicks "next", we display the next visitor's information.

Notable endpoints

Base endpoint: https://queueing.jisedu.or.id/api/{endpoint}