I deployed my laravel application on GCP App Engine
https://MY-PROJECT-NAME.appspot.com/
"Whoops, looks like something went wrong." is displayed.
I want to check a error log. but I couldn't find laravel.log.
Where can I see the log file.
According to the community documentation, you can specify the log-file in your app.yaml file as follows:
env_variables:
# Put production environment variables here.
APP_LOG: errorlog
Regarding the error message, it seems that you may be able to solve it by updating your installer and project with:
composer global update
composer update
You can find more information about that here
The laravel log will be inside your storage directory
storage/logs/laravel.log
Related
I deployed the laravel app to digitalocean:
but I don't understand why is it showing error 500??
I connected a github repo to deploy it to digitalocean.
1- I set the build commands to: composer install
2- environment variables are set: APP_NAME, APP_URL, APP_KEY, DATABASE_URL, APP_DEBUG
This is how the repo looks (private)
What seems to be the issue??
I just did check the repo and it seems the vendors folder not there and your build steps look like a typo issue so please run below command
composer install
Still you face the issue then refer the laravel logs for that what went wrong
you also dont have a .env file
maybe copy the .env.example to .env
perhaps follow the instructions on the laravel site for the version you are using.
in your question, you have spelt 'install' incorrectly
turns out there were typos of lower and upper cases in controllers according to the laravel log.
I fixed them and now the site is running. It's weird that these typos didn't trigger erorrs locally..
All You have to do is configure the .env file if u have a .example.env edit the file to .env if u dont have it just try to create one or clone one from another project and do composer install but don't forget to generate a key with php artisan key:generate in the end
I initially deployed my Laravel app with APP_DEBUG set to true, but now we're in production I don't want it to whoops! every time there's an error.
I've changed the contents of our EB .config file so that APP_DEBUG: false and I can see the change in Elastic Beanstalk's environment properties:
But Laravel itself is still dumping everything to the screen when there's an error.
I've tried ssh-ing into our server and running php artisan config:clear to see if it was that, but it still didn't work.
I don't understand why Laravel isn't respecting the updated configuration on deployment. Can anyone explain the logic here?
Update: I updated the security settings on the instance and noticed that it was giving our custom error screen. Can anyone explain what happened? Was restarting the server after running php artisan config:clear what did it?
I had issues like this before where I changed something in the console's environment properties which did not correspont with what I got using tinker. You can find the env file on your instance here:
/opt/elasticbeanstalk/deployment/env
if you open the file you see that variables set in .env are not quoted so if you have a password with for example a hashtag or a name with spaces it can result in unintended problems.
I would suggest to stop using environment variables via .yaml config files and start deploying your .env to the elastic beanstalk S3 bucket and fetching it on deployment. This will result in you having more control over the content of the file.
Example of this can be found here:
https://github.com/rennokki/laravel-aws-eb/blob/master/.ebextensions/00_copy_env_file.config
According to Frontend Quickstart official documentation of laravel-5.7. I run the command:
php artisan vendor:publish --tag=passport-components
I have no any error messages, it returns:
Copied Directory
[/vendor/laravel/passport/resources/assets/js/components] To
[/resources/assets/js/components/passport]
Publishing complete.
So, it does not copied to resources/js/components like the documentation stated:
The published components will be placed in your
resources/js/components directory.
I don't know why does it published in different path other than specified in the documentation? and how could I solve this issue?
In 5.7 the resources/assets/js directory became resources/js which has been causing issues.
There is an open issue about this on the passport github page: https://github.com/laravel/passport/issues/829
enter code hereHi all my on windows 7(so i don't have any folder permissions) I have can't see Laravel error anymore. It worked fine yesterday.
why? what's wrong?
Laravel version 5.1 and web server wamp lastest version.
I found this link
but can't find file - storage/meta/compiled.php
this command also not working for me - php artisan optimize
also debug = true in .env and app.php files
please help
If you read the installation documentation you will find the following information:
After installing Laravel, you may need to configure some permissions. Directories within the storage and the bootstrap/cache directories should be writable by your web server. If you are using the Homestead virtual machine, these permissions should already be set.
I have installed Laravel 4.2.11 on Wamp server through Composer. I have created the alias using wamp's Apache option but the URL http://localhost/laraveldemo/ (I have created the laraveldemo as alias) shows "Whoops, looks like something went wrong."
How I rectify this?
For further reference, when encountering a problem like this the first step to a solution is enabling the debug flag. That way you can often see a better error message.
This can be done through changing the flag located in app/config/app.php
'debug' => true
Should be set to true.