How orussy/orlibra works
Project type and purpose
• This is a full-stack web application (Node.js + Express) serving a library management interface (“ORlibra”).
• It uses server-side rendering (EJS templates), Mongoose models (MongoDB), and Firebase Admin SDK for authentication or push messages.
File structure
• Top-level:
• app.js → entry point, configures Express, routes, middleware
• firebaseconfig.js → Firebase Admin initialization
• models/ → Mongoose schemas (book.js, user.js)
• views/ → EJS templates for admin, student, book pages
• public/ → static assets: CSS, JS, fonts, images, vendor
• No separate “controllers” directory: routes and handlers are likely in app.js.
• Package.json lists dependencies, build scripts if any.
• There is a data.txt and a Firebase service account JSON.
README
• README just names the project: “ORlibra.” No extra architectural notes, so infer from code.
Detail
• Model layer separately (User, Book).