How ashutoshnegi880/role-based-access-control works
Project type and purpose
• This is a full-stack web application: a Role-Based Access Control (RBAC) Blog Platform.
• Purpose: allow users and admins to sign up, log in, view blogs; allow admins additionally to create and delete blogs.
File structure
• Top-level:
• app.js – the Express application entrypoint
• config/db.js – sets up the PostgreSQL connection
• controllers/ – definitions of request handlers (blogController.js, userController.js)
• services/ – business logic and data access abstractions (blogService.js, userService.js)
• routes/ – Express routers mapping URLs to controllers (blogRoutes.js, userRoutes.js, router.js)
• middleware/authMiddleware.js – JWT validation and role enforcement
• public/ – static frontend assets (HTML/CSS/JS for login, signup, blogs, admin)
• .env, package.json, etc. for configuration and dependencies
• Architecture implied:
• MVC-style layering (routes → controllers → services → database)
• Static asset delivery from the public folder
• Role-based JWT auth via middleware
README for additional insights
• Tech stack: Node.js + Express, PostgreSQL, JWT for auth, vanilla HTML/CSS/JS frontend
• Database schema: users and blogs tables, with foreign-key relationship on author_id
• Endpoints: /signup, /login, /blogs, /admin
• Dev workflow: npm scripts, .env for secrets, nodemon for hot reload
• Notes on middleware ordering: static → auth → routes → controllers → services → DB