sengabojr/skybook-airline-reservation

★ 18JavaScriptAudience · developerComplexity · 3/5Setup · moderate

Mindmap

mindmap
  root((skybook))
    Users
      Passengers
      Administrators
    Features
      Flight search
      Ticket booking
      Payment handling
      Reports
    Tech Stack
      React
      Node.js Express
      MongoDB
      Tailwind CSS
    Auth
      JWT tokens
      Role-based access
      Password hashing

mindmap root((skybook)) Users Passengers Administrators Features Flight search Ticket booking Payment handling Reports Tech Stack React Node.js Express MongoDB Tailwind CSS Auth JWT tokens Role-based access Password hashing

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Use as a reference for building a full-stack MERN application with JWT authentication and role-based access control

USE CASE 2

Study how to structure a React and Vite front end alongside an Express and MongoDB backend in a split-directory project

USE CASE 3

Fork and extend with features like QR code tickets or real-time seat availability as a learning exercise

Tech stack

JavaScriptReactNode.jsExpressMongoDBMongooseViteTailwind CSS

Getting it running

Difficulty · moderate Time to first run · 30min

Requires separate environment variable files configured for both the frontend and backend before either server will start.

In plain English

SkyBook is a web application for booking airline tickets and managing flight reservations. It is built as a student or educational project using a standard web development stack: React on the front end, Node.js and Express on the back end, and MongoDB as the database. The system is designed for two types of users. Passengers can create accounts, search for flights, view schedules and prices, book tickets, make payments, download their tickets, cancel reservations, and view their booking history. Administrators get a separate dashboard where they can create and manage flights, update schedules and destinations, set prices, monitor all reservations across the system, and generate reports. Authentication is handled with JSON Web Tokens and password hashing, with role-based access so passengers and administrators see different parts of the application. The payment module covers online payment handling, verification, and sending electronic receipts. Reporting covers reservation summaries, revenue figures, and passenger statistics broken down by day or month. The project is structured with separate frontend and backend directories. The front end uses Vite as its build tool and Tailwind CSS for styling. The back end runs on Express with Mongoose handling database interactions. Both sides need their own environment variable files configured before starting. The README notes the project is still in active development. Planned future additions include QR code tickets, real-time seat availability, and a mobile application. The codebase is organized with separate development branches for front-end and back-end work, with pull requests required before merging anything to the main branch. The project is described as educational in purpose.

Copy-paste prompts

Prompt 1

I forked skybook-airline-reservation and want to run it locally. Walk me through setting up the environment variable files for both the frontend and backend directories, then starting both servers.

Prompt 2

The skybook project uses JWT for auth with separate passenger and admin roles. Show me how the middleware checks the user role and how to add a new admin-only API route in the Express backend.

Prompt 3

I want to add QR code ticket generation to skybook. Which file handles the ticket download feature and how would I integrate a qrcode library to generate a code for each booking?

Prompt 4

How does the payment module in skybook work end to end? Walk me through from the frontend payment form to the backend verification step to sending the receipt.

Open on GitHub → Explain another repo

← sengabojr on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.