Hello,
This blog post is about quick tip for the users who have deployed Laravel application on Amazon EC2 instance.
Recently we had Laravel application deployed on Amazon EC2 instance where we put site on maintenance mode with command
php artisan down
Worked properly, site was in maintenance mode and displayed
Be Right Back screen.
After sometime we tried to make site up and running by
php artisan up
Didn't work as site was still displaying
Be Right Back screen
Tried to clear the cache and config with
php artisan cache:clear
php artisan config:clear
But still it didn't worked. After 5 to 10 mins to struggle, found out an issue. It was because of file permission issue. When you put site to maintenance mode, it creates
storage/framework/down folder
When you run
php artisan up
This folder should be removed. However in my case I was not using root user hence this file was not deleted.
So solution is
go to storage/framework folder and run command
rm -rf down
and that's it, your site is up and live.
Hope this helps you.
This blog post is about quick tip for the users who have deployed Laravel application on Amazon EC2 instance.
Recently we had Laravel application deployed on Amazon EC2 instance where we put site on maintenance mode with command
php artisan down
Worked properly, site was in maintenance mode and displayed
Be Right Back screen.
After sometime we tried to make site up and running by
php artisan up
Didn't work as site was still displaying
Be Right Back screen
Tried to clear the cache and config with
php artisan cache:clear
php artisan config:clear
But still it didn't worked. After 5 to 10 mins to struggle, found out an issue. It was because of file permission issue. When you put site to maintenance mode, it creates
storage/framework/down folder
When you run
php artisan up
This folder should be removed. However in my case I was not using root user hence this file was not deleted.
So solution is
go to storage/framework folder and run command
rm -rf down
and that's it, your site is up and live.
Hope this helps you.
No comments:
Post a Comment