{"id":13040,"date":"2026-10-12T10:21:41","date_gmt":"2026-10-12T10:21:41","guid":{"rendered":"https:\/\/ui-lib.com\/blog\/?p=13040"},"modified":"2026-10-13T17:26:57","modified_gmt":"2026-10-13T17:26:57","slug":"deploy-laravel-pos-shared-hosting-cpanel","status":"publish","type":"post","link":"https:\/\/ui-lib.com\/blog\/deploy-laravel-pos-shared-hosting-cpanel\/","title":{"rendered":"Deploy a Laravel + Vue POS on Shared Hosting (cPanel, Step by Step)"},"content":{"rendered":"\n
Many Laravel apps ask for a VPS because they need Node, Redis, a queue worker or a build step on the server. Stocky POS asks for none of those. It is a Laravel app with a Vue front end, and the front-end assets ship already built. So an ordinary cPanel shared hosting account is enough to run it.<\/p>\n\n\n\n
In this post we will install it from zero, step by step. We use Stocky POS as the example because it is the app we know best. The first five steps are the same for most Laravel apps on shared hosting: the right PHP version, an empty database, the files, a document root that points to public\/<\/code>, and the permissions. The installer part is specific to Stocky.<\/p>\n\n\n\n
What You Need<\/h2>\n\n\n\n
Let\u2019s take a look at what the server must have before we start:<\/p>\n\n\n\n
\n
PHP 8.2 or newer.<\/strong> Versions 8.2, 8.3 and 8.4 are supported.<\/li>\n\n\n\n
MySQL 8.0 or newer, or MariaDB 10.6 or newer.<\/strong><\/li>\n\n\n\n
Apache with mod_rewrite, or Nginx.<\/strong><\/li>\n\n\n\n
PHP extensions:<\/strong> bcmath, ctype, curl, fileinfo, gd, json, mbstring, openssl, pdo, pdo_mysql, tokenizer, xml and zip.<\/li>\n\n\n\n
Memory:<\/strong> set the PHP memory_limit<\/code> to 256 MB. Big imports and PDF exports are what use it.<\/li>\n\n\n\n
HTTPS<\/strong>, if you plan to scan barcodes with a phone camera or install the PWA. Browsers only offer those two on secure pages. The rest works without it.<\/li>\n<\/ul>\n\n\n\n
You do not need SSH, Composer, npm or phpMyAdmin. The installer checks every extension and names the missing ones, so you can also just start and see.<\/p>\n\n\n\n
Step 1: Set the PHP Version<\/h2>\n\n\n\n
In cPanel open MultiPHP Manager<\/strong> (some hosts call it Select PHP Version<\/strong>), choose your domain and set PHP to 8.2 or newer. While you are there, look at the extensions list. Control panels differ from host to host, so if you cannot find the option, ask your host\u2019s support to switch the version for you.<\/p>\n\n\n\n
Step 2: Create an Empty Database<\/h2>\n\n\n\n
Open MySQL Database Wizard<\/strong>. Create a database, create a user, and give that user all privileges on the database. Write down the database name, the username and the password. We need them in the installer.<\/p>\n\n\n\n
One thing about cPanel: it puts your account name in front of the database name, for example cpuser_stocky<\/code>, and it does the same for the database user. In the installer type the full name, prefix included.<\/p>\n\n\n\n
Do not import anything. Stocky creates every table by itself, so the database must be empty.<\/p>\n\n\n\n
Step 3: Upload the Files<\/h2>\n\n\n\n
Open File Manager<\/strong>, upload the application ZIP to the folder where the app will live and press Extract<\/strong>. Everything is included, so you do not run composer install<\/code> or npm.<\/p>\n\n\n\n
Step 4: Point the Domain at public\/<\/h2>\n\n\n\n
Now the tricky part, and the one people skip. Stocky is a Laravel app, and only the public<\/code> folder should be reachable from the web. Look at the folders we have after extracting:<\/p>\n\n\n
\nstocky\/\n .env\n storage\/\n bootstrap\/cache\/\n public\/ <- the domain must point here\n<\/pre><\/div>\n\n\n
If your domain points at the stocky<\/code> folder itself, anyone can download .env<\/code>. That file holds your database password and the application key.<\/p>\n\n\n\n
Which folder the domain points at decides what visitors can reach.<\/figcaption><\/figure>\n\n\n\n
In cPanel go to Domains<\/strong> and change the Document Root<\/strong> of your domain or subdomain to the public<\/code> folder. For example public_html\/public<\/code> if you extracted the app into public_html<\/code>, or stocky\/public<\/code> if it lives in its own folder.<\/p>\n\n\n\n
Some hosts do not let you change the document root. For that case Stocky ships an .htaccess<\/code> and a server.php<\/code> in the project root, and they send every request into public\/<\/code>. It works, but changing the document root is the cleaner fix.<\/p>\n\n\n\n
Step 5: Check the Permissions<\/h2>\n\n\n\n
The installer writes .env<\/code>, and the app writes uploads, so these must be writable:<\/p>\n\n\n\n
\n
.env<\/code><\/li>\n\n\n\n
storage\/<\/code><\/li>\n\n\n\n
bootstrap\/cache\/<\/code><\/li>\n\n\n\n
public\/images\/<\/code><\/li>\n<\/ul>\n\n\n\n
Folders at 755 and files at 644 is the normal setting. File Manager shows the permission of each item, and you can change it there.<\/p>\n\n\n\n
Step 6: Run the Installer<\/h2>\n\n\n\n
Now let\u2019s run the installer. Open https:\/\/your-domain\/setup<\/code> in the browser. Stocky installs itself in four screens.<\/p>\n\n\n\n
Screen 1: Requirements<\/h3>\n\n\n\n
The first screen lists the PHP version, every extension and the ZipArchive class, and each one gets a green tick when it passes. You cannot continue until all of them pass. If something is missing, switch it on in your hosting panel and press Re-check requirements<\/strong>. The installer has not written anything at this point.<\/p>\n\n\n\n
The requirements screen. A failing item is named, so you know exactly what to switch on.<\/figcaption><\/figure>\n\n\n\n
Screen 2: Application Settings<\/h3>\n\n\n\n
Here you set five things: the application name, the environment, debug mode, the application key and the application URL. For a live shop choose Production<\/strong> and turn debug Off<\/strong>. Press Generate<\/strong> to create the key. Type the URL the way visitors will, with https:\/\/<\/code>. Everything on this screen is saved to .env<\/code>, so you can change it there later.<\/p>\n\n\n\n
The defaults on a test install. On a live server set Environment to Production and Debug mode to Off.<\/figcaption><\/figure>\n\n\n\n
Screen 3: Database<\/h3>\n\n\n\n
Enter the host, port, database name, username and password from Step 2. Press Test connection<\/strong>. The Continue button only appears after the test passes.<\/p>\n\n\n\n
Use the database user from Step 2 here, with its full prefixed name.<\/figcaption><\/figure>\n\n\n\n
Screen 4: Review and Install<\/h3>\n\n\n\n
Read the summary and press Install Stocky<\/strong>. Now the installer does the real work. It writes .env<\/code>, builds the tables and fills in the starting data: the Owner role with its permissions, a default warehouse, currencies, payment methods, settings and the translations. On a slow host this can take a few minutes, so leave the tab open until it finishes.<\/p>\n\n\n\n
The last page gives you the administrator account that the install created. Sign in with it and change the password and the email at once.<\/p>\n\n\n\n
Step 7: Make Sure \/setup Is Closed<\/h2>\n\n\n\n
When the install finishes, the installer seals itself. After that, every \/setup<\/code> address answers 403. The seal is just a file:<\/p>\n\n\n
If \/setup<\/code> is ever reachable on a live site, check that file first. If it is missing, create it with any content and check the folder\u2019s permissions.<\/p>\n\n\n\n
Step 8: Set the Basics Before You Sell<\/h2>\n\n\n\n
Do these three things before the first sale, because they affect every document and report after it. Open Settings \u2192 System Settings<\/strong>:<\/p>\n\n\n\n
\n
Company details.<\/strong> Whatever you enter here appears on your receipts and invoices: the company name, logo, phone, email and address.<\/li>\n\n\n\n
Timezone.<\/strong> It decides which date a late-evening sale lands on, and what time the scheduled jobs run.<\/li>\n\n\n\n
Default currency.<\/strong> Reports and stock values are all calculated in this currency. If you switch on multi-currency later, the other currencies are converted into it.<\/li>\n<\/ul>\n\n\n\n
Then open Settings \u2192 Mail Settings<\/strong>, fill in your SMTP details and press Send test<\/strong>. Invoices, password resets and order confirmations all go through it. Many hosts only send mail from an address on your own domain, using port 587 with TLS.<\/p>\n\n\n\n
Step 9: Add the Cron Entry (Optional)<\/h2>\n\n\n\n
Stocky works without cron. Sales, stock, receipts, the online store and the reports do not need anything in the background. One cron entry unlocks the scheduled work, such as the daily database backup and the WooCommerce sync.<\/p>\n\n\n\n
In cPanel open Cron Jobs<\/strong> and add the line below to run every minute. If the default php<\/code> on your host is older than 8.2, write the full path to a newer PHP instead.<\/p>\n\n\n
The queue driver is the database, so there is no Redis to install and no separate queue:work<\/code> process. The scheduler drains the queue every minute. Without cron the queued jobs run while somebody uses the admin. That is enough for a small shop, but webhooks and syncs wait until the next visit.<\/p>\n\n\n\n
To check that it works, open Settings \u2192 System Health<\/strong> and look at the queue. A growing number of pending jobs means the scheduler is not running.<\/p>\n\n\n\n
System Health shows what the server is running and whether jobs are waiting in the queue.<\/figcaption><\/figure>\n\n\n\n
If the Install Fails<\/h2>\n\n\n\n
Most failures are one of these. The installer message tells you which:<\/p>\n\n\n\n
The message mentions<\/th>
What to do<\/th><\/tr><\/thead>
Access denied for user<\/td>
The database username or password is wrong. On cPanel check that you typed the prefixed username. Go back one screen and test again.<\/td><\/tr>
Unknown database<\/td>
There is no database with that name. Create the empty database in cPanel first, then type its full name with the prefix.<\/td><\/tr>
Permission denied \/ failed to open stream<\/td>
The installer cannot write to .env<\/code>, storage\/<\/code> or bootstrap\/cache\/<\/code>. Fix the permissions as in Step 5, and make sure the web server\u2019s user owns them.<\/td><\/tr>
Maximum execution time<\/td>
The install ran longer than PHP allows. Raise max_execution_time<\/code> to 300 and try again, or run the command-line install below.<\/td><\/tr>
Base table already exists<\/td>
An earlier attempt stopped halfway. Empty the database, or drop its tables, and start the installer again.<\/td><\/tr>
A blank page or a 500 after Install Stocky<\/td>
Set APP_DEBUG=true<\/code> in .env<\/code> to show the error, or open storage\/logs\/laravel.log<\/code>. Set debug back to false when you are done.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Problems After the Install<\/h2>\n\n\n\n
What you see<\/th>
Why, and what to do<\/th><\/tr><\/thead>
A 500 error or a blank page<\/td>
Open storage\/logs\/laravel.log<\/code>, or Reports \u2192 Error Logs<\/strong> in the admin. The usual causes are a permission on storage\/<\/code> or bootstrap\/cache\/<\/code>, or a PHP extension that disappeared when the host changed something.<\/td><\/tr>
Pictures will not upload<\/td>
Check that public\/images\/<\/code> is writable. Then check upload_max_filesize<\/code> and post_max_size<\/code> in PHP, because both must be larger than the file.<\/td><\/tr>
Emails do not arrive<\/td>
Mail Settings has a test button. Use it, then check the sender address and the port, as in Step 8.<\/td><\/tr>
The camera scanner or the install button is missing<\/td>
Both need HTTPS, and your site is on plain HTTP. Put an SSL certificate on the domain.<\/td><\/tr>
Pending jobs keep growing in System Health<\/td>
The cron entry is missing, or it uses the wrong PHP. See Step 9.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Prefer the Command Line?<\/h2>\n\n\n\n
If your host gives you SSH, you can skip the wizard. Write .env<\/code> with APP_URL<\/code>, APP_KEY<\/code> and the DB_*<\/code> values, then run:<\/p>\n\n\n
\nphp artisan key:generate\nphp artisan migrate --force\nphp artisan passport:install\nphp artisan db:seed --force\n\n# tell the installer it has nothing left to do\necho 1 > storage\/app\/public\/installed\n<\/pre><\/div>\n\n\n
These commands create the Owner role and the default administrator account. You can run the seeders twice and nothing is duplicated.<\/p>\n\n\n\n
Backups and Updates<\/h2>\n\n\n\n
Two things to set up on day one. First, backups. Open Settings \u2192 Backup<\/strong> and generate a dump. The dump is the database only, so include public\/images\/<\/code> and storage\/app\/<\/code> in your file backup too. Cloud backup to Amazon S3 or Google Drive is built in, and a copy that stays on the same server is not a safe copy.<\/p>\n\n\n\nThe backup page, with the list of dumps and the cloud backup option.<\/figcaption><\/figure>\n\n\n\n
Second, updates. Settings \u2192 Update<\/strong> takes the new ZIP, runs checks on the archive, the PHP version, permissions, disk space and the database, then installs it. It backs up the files and the database first, and rolls back by itself if something fails. Make your own database backup before each update as well, even though the updater makes one. If your host does not let the updater write files, use the Manual Update tab.<\/p>\n\n\n\nThe update page: drop in the new ZIP, let the checks run, then install.<\/figcaption><\/figure>\n\n\n\n
Is Shared Hosting Enough?<\/h2>\n\n\n\n
For one shop, or a few, yes. A $10 a month hosting plan does the job for most installs. If you outgrow it, your data is in your own database, so you can move it to a VPS later. The multi-tenant edition, Stocky SaaS, is different: on shared hosting an admin creates each tenant by hand, so a VPS is recommended there.<\/p>\n\n\n\n
![\"Diagram:](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-document-root-diagram-1024x538.png\")
![\"Stocky](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-installer-server-requirements-1024x783.jpg\")
![\"Stocky](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-installer-application-settings-1024x711.jpg\")
![\"\"](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-installer-database-1024x711.jpg\")
![\"\"](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-system-health-1024x783.jpg\")
![\"Stocky](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-settings-backup-1024x640.jpg\")
![\"Stocky](\"https:\/\/ui-lib.com\/blog\/wp-content\/uploads\/2026\/10\/stocky-settings-update-1024x783.jpg\")