Bobcares

Deploy Laravel API to cPanel | How To?

by | Jan 15, 2024

How to deploy Laravel API to cPanel? Read the article to find out. As part of our cPanel & WHM Support Services, Bobcares provides answers to all of your questions.

How to Deploy Laravel API to cPanel?

We must run the following steps in order to deploy Laravel API to cPanel:

1. Initially, make sure the Laravel API project is ready for the setup.

2. Then, get a hosting account with cPanel. Also, make sure that the server meets the minimal needs set out by the framework.

3. Now, enter the details in order to access the hosting account. Typically, cPanel offers a web-based interface for hosting account management.

4. In cPanel, create a subdomain or assign a domain for the Laravel API. In this stage, the needed subdomain or domain name is specified as well as linked to the correct server directory.

5. Then, upload the files for the Laravel API project to the directory linked to the subdomain or domain we created in the previous step using the File Manager in cPanel or an FTP client. Make sure we include the public folder along with all other required files and directories for the Laravel app.

6. Also, make sure the Laravel project’s files are runnable and server-accessible by adjusting their permissions. Typically, this stage entails giving folders and files the proper permissions.

7. Then, create a database for the Laravel API in cPanel. Now, give the rights to a user. Also, note the hostname, password, username, and DB name.

8. Find the .env file in the root directory of the project, then edit the database connection settings. Assume that the hostname, password, username, and database name correspond to the ones we created in the previous step.

9. Also, install the dependencies listed in the composer.json file by using the composer install code in the root directory of the Laravel project via SSH.

10. In order to create a unique app key and delete the app cache, run the following codes while we’re still in the root directory of the Laravel:

deploy laravel api to cpanel

11. Now, set up the web server to match the Laravel API settings in cPanel. Usually, this entails setting up Nginx rules or writing an Apache .htaccess file to direct queries to the Laravel app’s public folder.

12. Lastly, to make sure the API is working properly, use a web browser to access the domain connected to it. We can do the basic API tests to confirm functionality.

[Searching solution for a different question? We’re happy to help.]

Conclusion

We should be able to deploy the Laravel API to cPanel and enable user access by following these steps provided by our Support team in this article.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF