How to install and monitor Laravel on cPanel

Valerio Barbera

Laravel is one of the most popular PHP frameworks today for creating modern web applications. In this tutorial, you’ll discover how to set up a Laravel project on cPanel.

To install and use Laravel you must have composer installed in your system. Let’s first clarify what Composer is and what it means in Laravel before continuing.

What is cPanel?

cPanel is a user-friendly control panel used to streamline website and server management. It is an online GUI that is based on Linux. You may publish websites, manage domains, arrange web files, create email accounts.

The WebHost Manager administration interface allows users to manage their websites, and also provides hosting providers with the tools they need to manage the server.

What is Composer?

Composer is the package manager of the PHP ecosystem. 

With composer, you can install third-party libraries, create and distribute your own modules, and automate php application installation and distribution. 

So before utilizing Laravel, make sure Composer is set up on your machine.

Step 1: Create subdomain

You can open the cPanel administration dashboard at the port 2083 or “cpanel” subdomain: http://yourdomain.com:2083 or https://cpanel.yourdomain.com

To enter a new subdomain for your brand-new Laravel project, click Subdomain under the Domain menu. If you want to host it under the main domain, skip this section.

Because the Laravel project starts from the public folder, enter the name of the subdomain, such as “myapp”, and place “public_html/myapp” under the documents root. 

Step 2: Create database

To enter a new database for your brand-new Laravel project, click MySQL database wizard under Databases.

Enter the name of the database such as “myapp_db”.

To access the database, create a new user account. Give the newly created database user all the privileges, then click the next button. Save all of this information. You need them to configure the database connection in your Laravel project .env file.

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=xxxx
DB_USERNAME=xxxx
DB_PASSWORD=xxxx

Step 3: Configure Composer 

A Laravel project can be loaded into cPanel in two different methods. Using File Upload, or the Terminal. In this tutorial, we’ll use Terminal to take advantage of Composer to pull it out.

Since Composer is installed as a remote script, you need to make sure that the allow_url_fopen directive is enabled in the .bashrc configuration file in your server.

Run the command below in your terminal:

echo 'alias composer="php -d allow_url_fopen=On /home/$USER_NAME/composer.phar"' >> ~/.bashrc source ~/.bashrc

Download composer using the below command. Curl will give you an error message if you attempt to connect to a website that has a self-signed SSL certificate because curl was unable to validate the certificate. 

In that situation, you could omit certificate validation by using the -k or —insecure flag.

The -O option will save the file with the same name as the remote in the current working directory.

curl -k -O https://getcomposer.org/installer

Set up composer using:

php -d allow_url_fopen=On installer

Step 4: Bring your application into the server

To organize your application, make a folder. Consider the folder myapp and place your project there.

mkdir myapp
cd myapp
git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY .

Step 5: Install dependencies

Composer install dependencies in the vendor directory inside your project:

composer install

Make a fresh application key. This command modifies the APP_KEY setting in your .env file.

php artisan key:generate

Next you must configure the database connection with credentials created at the Step 2:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=xxxx
DB_USERNAME=xxxx
DB_PASSWORD=xxxx

Next, migrate your database. With this command, all of our schemas are published to the database. The database table is also created by this operation.

php artisan migrate

Establish the proper permissions for the storage folder:

chmod -R 775 storage

Step 6: Make your app publicly accessible

To make your application publicly accessible it should be loaded into the public_html folder of the webserver.

To link the installation of your application with the public_html folder of the webserver, just create a symbolic link.

ln -s /home/user/myapp/public /home/user/public_html

A symbolic link, or symlink, is a file or folder on your computer that points to another file system that is connected to it.Do the same for the storage directory:

ln -s /home/user/my_laravel_app/storage/my_laravel_app/public
/home/user/public_html/storage

Then activate the storage link by running the following command:

php artisan storage:link

Monitoring your application

What if you want to monitor how your users experience your application? For example, how much time does it take to load a page? Is an API endpoint broken? Are there any database errors?

In order to answer these kinds of questions consider trying Inspector, a Code Execution Monitoring tool built for developers.

With Inspector you don’t need to install anything at the server level. It works with a simple composer package.

Follow this tutorial to add real-time monitoring to your Laravel application: 

Related Posts

[Resolved] Integrity constraint violation – Fast tips

If you are dealing with the error: “Integrity constraint violation: Cannot add or update a child row: a foreign key constraint fails“, you are in the right article. Usually you encounter this error when you add a new column to a table and declare it as a Foreign Key.  In a SQL database, a foreign

How to monitor Guzzle Http Client – PHP Fast tips

Guzzle is a popular PHP HTTP client that makes it easy to send HTTP requests and create web service libraries. The most popular PHP frameworks provides an internal Http Client service, and they are simply a customized implementation of the Guzzle Http Client: Guzzle is widely used for two main reasons: Customization and Flexibility For

Post your Feature Requests and contribute to our product journey

I’ve recently been thinking about the best way to allow Inspector’s users to share the features they’d like to find in Inspector. Often I ask for feedback or investigate new feature requests during live chat sessions. In the first instance developers drop in a live chat asking for support. Very often these chats lead to