How this project works
Eastwharf is the Laravel remake of Westloop: a neighborhood social network with accounts, profiles, follows, likes, comments, a following timeline, search, notices, and a real Ubuntu VPS deploy. Each numbered folder in fcc-laravel-social is a working snapshot.
The stack, and why these tools
| Job | Choice | Why |
|---|---|---|
| Language / framework | PHP, Laravel 11 | Laravel’s Eloquent and policies are built for ownership and graphs. A Follow model with a unique (follower_id, following_id) pair is ten lines. PHP-FPM + Nginx is the default VPS path. |
| Database | PostgreSQL | Follows, likes, and comments need foreign keys and unique pairs. SQLite is only for the first laptop boot. |
| CSS | Tailwind CSS | Feeds, avatars, and a sticky nav are layout-heavy. Utilities stay in the templates you already edit. |
| JavaScript | Livewire (or HTMX) + Alpine.js | Livewire or HTMX both keep writes on the server. Alpine ships with Laravel’s usual stack. Avoid a Vue SPA for likes. |
| Authentication | Laravel session guard (no Breeze required) | Hand-wire the web guard. Hash with bcrypt. Policies protect compose, edit, and delete. |
| Process / proxy | PHP-FPM, Nginx, Let’s Encrypt | Same VPS shape as Westloop: one app process, Postgres on localhost, Nginx for TLS and static/media files. |
| Hosting / DNS | Hetzner Cloud CX22 (or Contabo / DigitalOcean), Cloudflare Registrar + DNS | You own the box. PaaS is easier and teaches less. |
| Console locally, Postmark in production | Password reset must leave the laptop. |
If you already finished the Laravel blog, keep going — this project adds a social graph and a VPS ship, not another CRUD journal.
Parts in order
Work through the parts in sequence. Each lesson explains the ideas, then points you to a runnable GitHub snapshot.