Page title shows "Laravel" — APP_NAME is inconsistent across environments #120

New issue

Closed

opened 2026-08-01 17:24:40 +02:00 by myrmidex · 0 comments

myrmidex commented

2026-08-01 17:24:40 +02:00

Owner

Summary

Browser tab titles show the wrong application name. Locally it reads "Laravel"; in production it reads "Lemmy Poster" — an old project name. Neither is correct.

Root cause

config/app.php:16:

'name' => env('APP_NAME', 'Laravel'),

The layouts pass 'FFR' as a fallback:

<title>{{ config('app.name', 'FFR') }}</title>

but that fallback never fires — config('app.name') always resolves to something, so the second argument is dead. Whatever APP_NAME holds (or 'Laravel' when unset) is what renders.

Three sources disagree

Source	Value
`config/app.php:16` (default when unset)	`Laravel`
`.env.example:1`	`Laravel`
`docker/build/laravel.env:1` (production)	`Lemmy Poster`
`docker/dev/docker-compose.yml:22`	`FFR`

So production titles currently read "Lemmy Poster", a name predating this project.

Affected

resources/views/layouts/app.blade.php:8
resources/views/layouts/guest.blade.php:8
resources/views/layouts/onboarding.blade.php:8 (renders as {name} - Setup)

.env.example also derives MAIL_FROM_NAME and VITE_APP_NAME from APP_NAME, so both inherit the wrong value.

Proposed

Settle on one name and apply it consistently. Suggested: FFR (matches the dev compose value and the repo name), though "Fedi Feed Router" may read better in a browser tab — worth a quick decision.

Update config/app.php default from Laravel to the chosen name
Update .env.example
Update docker/build/laravel.env (fixes the production "Lemmy Poster" title)
Leave docker/dev/docker-compose.yml if it already matches
Consider dropping the now-dead 'FFR' fallback argument in the three layouts, since it is misleading — it looks like a safety net but can never trigger

Acceptance criteria

Name chosen and applied to all four sources
Browser tab shows the correct name in dev and production
Onboarding layout still renders {name} - Setup
No remaining references to "Laravel" or "Lemmy Poster" as the app name

Branding work (sidebar logo and favicon still use stock Laravel assets) is tracked separately — this ticket is text only and has no design dependency.

## Summary Browser tab titles show the wrong application name. Locally it reads "Laravel"; in production it reads "Lemmy Poster" — an old project name. Neither is correct. ## Root cause `config/app.php:16`: ```php 'name' => env('APP_NAME', 'Laravel'), ``` The layouts pass `'FFR'` as a fallback: ```blade <title>{{ config('app.name', 'FFR') }}</title> ``` but that fallback **never fires** — `config('app.name')` always resolves to something, so the second argument is dead. Whatever `APP_NAME` holds (or `'Laravel'` when unset) is what renders. ## Three sources disagree | Source | Value | |---|---| | `config/app.php:16` (default when unset) | `Laravel` | | `.env.example:1` | `Laravel` | | `docker/build/laravel.env:1` (production) | `Lemmy Poster` | | `docker/dev/docker-compose.yml:22` | `FFR` | So production titles currently read **"Lemmy Poster"**, a name predating this project. ## Affected - `resources/views/layouts/app.blade.php:8` - `resources/views/layouts/guest.blade.php:8` - `resources/views/layouts/onboarding.blade.php:8` (renders as `{name} - Setup`) `.env.example` also derives `MAIL_FROM_NAME` and `VITE_APP_NAME` from `APP_NAME`, so both inherit the wrong value. ## Proposed Settle on one name and apply it consistently. Suggested: **FFR** (matches the dev compose value and the repo name), though "Fedi Feed Router" may read better in a browser tab — worth a quick decision. - Update `config/app.php` default from `Laravel` to the chosen name - Update `.env.example` - Update `docker/build/laravel.env` (fixes the production "Lemmy Poster" title) - Leave `docker/dev/docker-compose.yml` if it already matches - Consider dropping the now-dead `'FFR'` fallback argument in the three layouts, since it is misleading — it looks like a safety net but can never trigger ## Acceptance criteria - [ ] Name chosen and applied to all four sources - [ ] Browser tab shows the correct name in dev **and** production - [ ] Onboarding layout still renders `{name} - Setup` - [ ] No remaining references to "Laravel" or "Lemmy Poster" as the app name ## Related - Branding work (sidebar logo and favicon still use stock Laravel assets) is tracked separately — this ticket is text only and has no design dependency.