Skip to content
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

Building with APP_NAME=Laravel cause error #149

Open
IvanSerpa opened this issue Aug 4, 2023 · 3 comments
Open

Building with APP_NAME=Laravel cause error #149

IvanSerpa opened this issue Aug 4, 2023 · 3 comments
Assignees
Labels
bug Something isn't working linux

Comments

@IvanSerpa
Copy link

What happened?

The executable generated by php artisan native:build linux only renders the generic "500 SERVER ERROR" page.
php artisan native:serve renders the page correctly.
Changing APP_NAME in .env to anything other than "Laravel" bypasses the issue and the page renders correctly.

How to reproduce the bug

Fresh install of Laravel.
Fresh install of NativePHP.
Leave APP_NAME=Laravel in .env file.
Run php artisan native:build linux.
Run the executable.

Package Version

0.3.3

PHP Version

8.2.8

Laravel Version

10.17.1

Node Version

20.4.0

Which operating systems does with happen with?

Linux

Notes

Changing debug to true in config/app.php makes the executable generated by php artisan native:build linux work even with APP_NAME=Laravel, and it doesn't show any errors.

@IvanSerpa IvanSerpa added the bug Something isn't working label Aug 4, 2023
@simonhamp simonhamp self-assigned this Apr 30, 2024
@simonhamp simonhamp changed the title [Bug]: building with APP_NAME=Laravel cause error building with APP_NAME=Laravel cause error May 8, 2024
@simonhamp simonhamp changed the title building with APP_NAME=Laravel cause error Building with APP_NAME=Laravel cause error May 8, 2024
@simonhamp
Copy link
Member

@IvanSerpa I've not been able to reproduce this. Does it still occur for you?

@Dalovec
Copy link

Dalovec commented Aug 6, 2024

@simonhamp
I've actually encountered that hot reloading doesn't work if the App name is Laravel. So there might be something to this.
Reproduction:

  • make a new project
  • add tailwind and add @vite to welcome.blade.php
  • npm run dev
  • php artisan native:serve
  • add any text or something to try hot reloading

With blade changes (html content) you must restart the dev server and css/js doesn't actually change unless you run npm run build.
If you change the app name suddenly everything works as intended.

@simonhamp
Copy link
Member

@Dalovec I'm not able to reproduce what you're seeing, but that feels like a separate issue to me.

@IvanSerpa for production builds, 500 errors should get logged into [APPDATA]/storage/logs/* - do you see any errors there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working linux
Projects
None yet
Development

No branches or pull requests

3 participants