First full-stack build · 2021
Chainlink
A blockchain forum and social app — my first Laravel and Vue build: questions, replies, categories, likes and notifications in MySQL, with replies updating live over Pusher.
No live link — the original database and API keys are long gone, so the repository is the record.

01What the build involved
01
A forum with four tables that matter
Questions, replies, categories and likes, plus the notifications table Laravel gives you. Resource routes cover questions, categories and replies, and two small endpoints handle like and unlike. The schema carries the rules: a reply belongs to a question and a user, a like belongs to a reply and a user, and a category groups questions. Getting those relationships right before writing a screen was the actual lesson of the project.
02
JWT instead of sessions
Because the front end is a Vue app talking to a JSON API, auth runs on tymon/jwt-auth with signup, login, logout, refresh and me under /api/auth, rather than Laravel’s session guard. The Laravel side still serves the app: three catch-all web routes return the same view, so opening /question/some-slug directly or refreshing that page does not 404 — the detail that makes a history-mode router feel like a real site.
03
Live replies, and the first inbox
LikeEvent and DeleteReplyEvent implement ShouldBroadcast and go out over Pusher, so a like in one browser lands in another without a refresh, and a database notification feeds an inbox screen. Vue Router with Vuetify and a markdown editor handled the writing side. It is the project where the back end stopped being a mystery: routes, middleware, events and migrations all had to agree before anything worked.
02What it left behind
Outcome
A working forum — questions, replies, categories, likes and notifications, with replies broadcast over Pusher and a JWT-guarded API. No deployment survived the years, but the migrations and the Vue app are still in the repository and still run locally, which is what this case study is built from.
Another pass
A JWT in localStorage with a refresh endpoint is the first thing I would change: an httpOnly cookie keeps the token out of anything a script can read. I would also write the API tests before the screens, because the reply and like rules were the parts I broke most while building the interface.
03Inside the product
Click any screenshot to view it full size