Skip to content

fix: use app name as project name instead of directory name #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 13, 2025

Conversation

calebdw
Copy link
Contributor

@calebdw calebdw commented Aug 13, 2025

Hello!

When running inside of Docker, boost thinks the project name is html which is a little strange:

image

@calebdw calebdw force-pushed the calebdw/push-trorwrtmxlkk branch from f09b9c6 to 14d6a66 Compare August 13, 2025 17:25
@calebdw calebdw force-pushed the calebdw/push-trorwrtmxlkk branch from 14d6a66 to a58a90e Compare August 13, 2025 19:07
@ashleyhindle
Copy link
Collaborator

Ah good point 🤔 Though when running a brand new project the app name is 'Laravel', which actually works in that sentence to be fair, but it's also inaccurate 😁

@calebdw
Copy link
Contributor Author

calebdw commented Aug 13, 2025

I guess we could check if the name is Laravel and fall back to the directory name?

@ashleyhindle
Copy link
Collaborator

I guess we could check if the name is Laravel and fall back to the directory name?

Aye I was just wondering about that, but I couldn't convince myself it was the right thing. config('app.name'); is better for now and we can revisit this later if needed 💪

@ashleyhindle ashleyhindle merged commit e3487b2 into laravel:main Aug 13, 2025
9 checks passed
@calebdw calebdw deleted the calebdw/push-trorwrtmxlkk branch August 13, 2025 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants