This tutorial is ideal for developers who prefer using the htdocs folder structure instead of the traditional /var/www directory.

Prerequisites

Before starting, ensure you have:

• A Linux server with SSH access
• GitHub repository of your Laravel project
• Apache/XAMPP or LAMP stack installed
• PHP and Composer installed
• Database access (MySQL/MariaDB)
• Basic Linux command knowledge

Step 1: Connect to Your Linux Server

Login via SSH from your local machine:

ssh username@server_ip

Example:

ssh myeventadmin@your_server_ip

Step 2: Update Your Server

Always update packages before setup:

sudo apt update && sudo apt upgrade -y

Step 3: Install Required Packages

Install Apache, PHP, Git, Composer dependencies, and tools:

sudo apt install apache2 mysql-server unzip git curl -y

Install PHP extensions required by Laravel:

sudo apt install php php-cli php-mysql php-zip php-gd php-mbstring php-curl php-xml libapache2-mod-php -y

Check PHP version:

php -v

Step 4: Install Composer

cd ~
curl -sS https://getcomposer.org/installer | php
sudo mv composer.phar /usr/local/bin/composer

Verify installation:

composer -V

Step 5: Move to HTDOCS Directory

Depending on your server setup, the htdocs directory may be located at:

/opt/lampp/htdocs

or

/var/www/html

Navigate to htdocs:

cd /opt/lampp/htdocs

Step 6: Clone Laravel Project from GitHub

sudo git clone https://github.com/username/project.git

Move into project folder:

cd project

Step 7: Set Folder Permissions

sudo chown -R daemon:daemon /opt/lampp/htdocs/project
sudo chmod -R 775 storage
sudo chmod -R 775 bootstrap/cache

(If using Apache instead of XAMPP, replace daemon with www-data)

Step 8: Configure Environment File

Create the environment file:

cp .env.example .env
nano .env

Update important settings:

APP_NAME=Laravel
APP_ENV=production
APP_DEBUG=false
APP_URL=http://yourdomain.com

Add your database credentials as well.

Step 9: Install Laravel Dependencies

composer install

Step 10: Generate Application Key

php artisan key:generate

Step 11: Create Database and Run Migration

Login to MySQL:

sudo mysql

Create database:

CREATE DATABASE laravel_db;
EXIT;

Run migrations:

php artisan migrate

Step 12: Configure Apache to Use Public Folder

Edit Apache configuration:

sudo nano /opt/lampp/etc/extra/httpd-vhosts.conf

Add:

<VirtualHost *:80>
    ServerName yourdomain.com
    DocumentRoot "/opt/lampp/htdocs/project/public"

    <Directory "/opt/lampp/htdocs/project">
        AllowOverride All
        Require all granted
    </Directory>
</VirtualHost>

Restart Apache/XAMPP:

sudo /opt/lampp/lampp restart

Step 13: Test Laravel Application

Open browser:

http://your_server_ip/project/public

or

http://yourdomain.com

If everything is configured properly, your Laravel website will be live.

Important Production Tips

• Always set APP_DEBUG=false
• Never make .env publicly accessible
• Ensure correct folder permissions
• Use SSL (HTTPS) for live websites
• Regularly pull updates from GitHub

Conclusion

Deploying a Laravel project using the htdocs directory and GitHub cloning is a practical and efficient workflow for Linux servers running XAMPP or Apache environments. By following this step-by-step process — cloning the repository, configuring environment variables, setting permissions, and configuring Apache — you can successfully deploy your Laravel application in a production-ready environment.

This method is especially useful for developers who prefer traditional htdocs-based hosting environments while maintaining version control through GitHub.

The post How to Deploy a Laravel Project on a Linux Server Using HTDOCS and GitHub – Complete Step-by-Step Guide appeared first on Artificial Intelligence.

Understanding the Problem

If you’re encountering a HTTP 500 Error with your Laravel project in cPanel, the issue typically lies in your .htaccess configuration or file permissions. This comprehensive guide will help you resolve both issues step by step.

The .htaccess Configuration Fix

The Problem with Your Current Setup

Your current .htaccess file contains duplicate RewriteEngine directives and conflicting rules, which causes the 500 Internal Server Error.

Solution: Separate .htaccess Files

You need two separate .htaccess files in different locations:

1. Root .htaccess File

Location: public_html/bangaloreorbit.com/.htaccess

RewriteEngine On

# Redirect all requests to the public folder
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ public/$1 [L]

2. Public Folder .htaccess File

Location: public_html/bangaloreorbit.com/public/.htaccess

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Send Requests To Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

Alternative: Single .htaccess Solution

If you prefer using a single .htaccess file, use this configuration in your root directory:

RewriteEngine On

# Redirect all requests to the public folder
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ public/$1 [L]

# Public folder rules
RewriteRule ^public/(.*)$ public/$1 [L]

Complete File Permissions Guide

Why Permissions Matter

Incorrect file permissions are a common cause of Laravel 500 errors. The web server needs appropriate read/write access to function properly.

Method 1: Check Permissions via cPanel File Manager

1. Login to cPanel
2. Open File Manager
3. Navigate to public_html/bangaloreorbit.com
4. Right-click on folders and check Permissions
5. Verify these ideal permissions:

• Folders: 755
• Files: 644
• Storage/Cache folders: 755 or 775

Method 2: SSH Commands for Permission Management

If you have SSH access, use these commands:

Check Current Permissions

# Check folder permissions
ls -la /home/yourusername/public_html/bangaloreorbit.com/

# Check .htaccess file permissions
ls -la /home/yourusername/public_html/bangaloreorbit.com/public/.htaccess

Set Correct Permissions

# Basic folder permissions (755)
chmod 755 storage/
chmod 755 bootstrap/cache/
chmod 755 public/

# File permissions (644)
chmod 644 .htaccess
chmod 644 public/.htaccess
chmod 644 index.php

# Writable directories (775)
chmod 775 storage/
chmod 775 bootstrap/cache/
chmod 775 storage/logs/
chmod 775 storage/framework/

Method 3: cPanel Permission Setup Steps

1. Open File Manager in cPanel
2. Navigate to your Laravel project folder
3. Select the folder/file and click Permissions
4. Enter the appropriate numeric value:

• 755 for folders
• 644 for files

1. Click Change Permissions

Laravel-Specific Permission Requirements

Critical Writable Directories

# Make storage and cache directories writable
chmod -R 775 storage/
chmod -R 775 bootstrap/cache/

# Protect environment file
chmod 644 .env

Recursive Permission Setting

# Set permissions for entire Laravel project
find /path/to/your/laravel/project -type f -exec chmod 644 {} \;
find /path/to/your/laravel/project -type d -exec chmod 755 {} \;

# Special permissions for storage and cache
chmod -R 775 storage/
chmod -R 775 bootstrap/cache/

Permission Checklist ✅

Use this checklist to verify your setup:

• [ ] Root folder: 755
• [ ] Public folder: 755
• [ ] Storage folder: 775
• [ ] bootstrap/cache: 775
• [ ] .htaccess files: 644
• [ ] All other files: 644
• [ ] .env file: 644 (readable but protected)

Troubleshooting Common Issues

1. Still Getting 500 Error?

• Check cPanel error logs
• Verify mod_rewrite is enabled in Apache
• Ensure PHP version compatibility
• Check Laravel storage logs: storage/logs/laravel.log

2. Permission Denied Errors?

# Reset ownership (if you have SSH access)
chown -R username:username /path/to/laravel

# Or set more permissive permissions temporarily
chmod -R 755 storage/
chmod -R 755 bootstrap/cache/

3. White Screen of Death?

• Check Laravel logs: storage/logs/laravel.log
• Verify .env configuration
• Clear cache: php artisan config:clear

Pro Tips for cPanel Laravel Deployment

1. Always backup before making permission changes
2. Use 755 for folders, 644 for files as the standard
3. Test thoroughly after each permission change
4. Monitor error logs regularly
5. Keep Laravel updated for security patches

Conclusion

By following this guide, you should be able to resolve the HTTP 500 error in your Laravel application. Remember:

1. Fix .htaccess configuration by separating rules into appropriate files
2. Set correct file permissions using the guidelines provided
3. Test your application after each change
4. Monitor logs for any additional issues

If problems persist, check your cPanel error logs or Laravel storage logs for more specific error messages that can help pinpoint the exact issue.

The post Complete Guide to Fix Laravel .htaccess 500 Error and File Permissions appeared first on Artificial Intelligence.