How brandon-gomez/booksharing_socialnetwork works
Project type and purpose
• This is a full-stack web application composed of:
• A Vue.js single-page frontend (directory “fronvue”)
• A Node.js/Express backend API (directory “backnode”)
• A MySQL (or compatible SQL) database (SQL dumps in backnode)
• Firebase as an external file storage service
• Local filesystem storage for uploaded PDFs (backnode/uploads)
• The app exposes REST endpoints for users, posts, likes, follows, categories, file uploads, and admin functions. JWT middleware secures protected routes.
File structure
• Top-level directories:
backnode/ ← Express API
• app/index.js ← server bootstrap
• controllers/ ← MVC controllers
• models/ ← ORM or model definitions
• routes/ ← Express route definitions
• database/ ← DB connection and Firebase setup
• middlewares/ ← JWT authentication
• uploads/ ← local file storage for book PDFs and profile images
• .env ← secrets (DB creds, JWT secret, Firebase key path)
fronvue/ ← Vue CLI frontend
• .env ← API endpoints, Firebase config
• babel.config.js
• jsconfig.json
• dist/ ← compiled production assets
• Build & run: uses “concurrently” to start backnode in dev mode and serve the Vue app.
Key insights from README
• You must import the SQL schema (bd-27-5.sql) into your local database.
• You need a Firebase service-account JSON and a .env file for private keys.
• Run both servers in parallel:
concurrently "npm run dev --prefix backnode" "npm run serve --prefix fronvue"
Detail
• Environment variables feeding into components (.env → DB connection, JWT secret, Firebase JSON).
• Don’t omit the build/deploy boundary—dist/ assets vs. dynamic API.