I have Laravel application which I learned to run both with php artisan serve and with local Apache.
Now I wish to run the same on Amazon Beanstalk.
I have created Beanstalk instance for PHP7. Then I went to Amazon Linux console and installed composer there. I think this was unneeded step.
Next I acrhived all my Laravel project with ZIP and uploaded it to AWS with web console. First I got Forbidden error
as said here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-laravel-tutorial.html
Then I fixed document root to public/ as said below and now I have health state severe saying
Impaired services on all instances.
Following services are not running: proxy.
When I am opening site with browser, I see blank page.
How to see any logs in AWS to understand what is happening?
What cen be a reason? Project is self-contained, it uses SQLite database inside the codebase. When I was enabling this project on local machine, I was to enable multiple things in Apache and PHP.
It was the problem with ZIP file structure: it contained extra top directory inside. So, on AWS it was /var/app/current/myappname while should be just /var/app/current.
Did you install mbstring after creating the instance?
sudo yum install php70w-mbstring
If this isn't the problem, you can view Laravel log in storage/log/laravel.log and tell us what is there to help you.
I was getting this error due to Elastic Beanstalk config settings being incorrect, specifically, the Document root was incorrect and was seeing the Following services are not running: proxy. error in the event log.
When generating the ZIP archive, be sure to generate it within the project folder. So when you open the zip file, you have the app folder, not another folder with the project name.
Related
Has anyone here been able to install Snipe-IT (Open source asset management: https://snipe-it.readme.io/docs) on Azure Web Apps?
I know it is possible to install it on an Azure VM, since I've done that, but I would prefer it to be on a Web App so we keep everything simple and slightly more secure.
I have been able to download it from GitHub, and it then says that the document root is incorrect (It has to be \wwwroot\public instead of \wwwroot). So, I go ahead and change the document root to the public, but then the page returns a 500 error. I see that I need to install Composer, so I install the extension for that, but nothing changes. I know the document root works correctly because I am able to place a test file in the public directory and it works fine. It is just the actual Snipe-IT install that gets screwed up.
Here's how I did it:
Run the command composer install under \wwwroot folder to install dependencies.
Change the document root by setting the virtual application path for the web app.
Edit the Snipe-IT configuration file (.env file) to configure the database credentials, app key and so on.
Restart the app service.
Finally, It worked for me.
I want to install Laravel on my web server using softaculous available in my Cpanel but I get the following errors:
The following errors were found :
Could not write the Configuration File app.php
Could not write the Configuration File composer.json.
What might I have done wrong?
You are trying to update some files within your laravel application. The problem is that you don't have the right to do so.
What you could do is:
1. Check the file permissions and correct them.
2. Connect to your web server over ssh and try to install it.
I've already installed composer on the production application. I've set permissions on the storage folder (775, 777). The web server is configured to look for index.php. That's the first time I try to deploy a Laravel application. Something that messed me up was that after I used the push command to upload my Laravel application using git I looked inside the Laravel storage folder in the server and I realized that the storage folder had basically only the directory structure of the storage folder of my local Laravel application, many files were missing like laravel.log among others. I assumed that it was because I didn't ran composer install on the server. After running composer install things continued the same.
A deployment of a new PHP app fails with Composer, in the deployment logs, that are located in
D:\home\site\deployments\long-alphanumerical-string\log.log
I see the following:
Could not open input file: D:\home\SiteExtensions\ComposerExtension\Commands\\composer.phar,,0
The same setup works on other environments of the application without any problem.
Check if the Composer extension is added on the Extensions blade
It's possible that your composer installation didn't work well. Check if the mentioned file exists, if it doesn't - get it from https://getcomposer.org/download/ (phar files are at the bottom of the page), upload it via kudu and Redeploy the application.
While installing laravel through terminal command, my other projects in MAMP htdocs folder got affected and they are not working.
I followed this process for installing laravel
Those directions have you symlink the "htdocs" directory to your laravel install, effectively making your htdocs directly useful only for Laravel.
You should avoid this, perhaps by creating a symlink from your laravel build to a directory within htdocs. For example, linking to a directory in htdocs called "mylaravelapp": ln -s /path/to/laravel-master /path/to/htdocs/mylaravelapp.
Lastly, consider using Vagrant or another virtual machine provider instead of MAMP for a server. You'll have to get through a learning curve (potentially), but you'll end up better for it. This creates a virtual server for you, which won't interact with any other parts of your Mac (YOu can make a server per project!).
Here is a guide to get started with Laravel 4 and Vagrant.