Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Deploying Laravel on a shared hosting using only .htaccess

Deploying Laravel on a shared hosting using only .htaccess

Making Laravel work on a shared hosting can be troublesome, because Laravel needs to have its document root set to the public directory. This may not be configurable by a user or even desirable, when the server is hosting multiple websites.

Here's a simple method using only a .htaccess file placed in Laravel's root directory - e.g. alongside app, bootstrap, config, ... No changes whatsoever are necessary to your code.

The file rewrites all the requests so that requesting /file.png would in fact return /public/file.png and anything else is routed to /public/index.php. This also ensures that nothing outside the public folder can be accessed, thereby protecting any sensitive files like .env or database/*.

The simple method

This method assumes that DOCUMENT_ROOT is set properly by your Apache server. Try this first and use the 2nd method only if it doesn't work on your server.

.htaccess

RewriteEngine on

# serve existing files in the /public folder as if they were in /
RewriteCond %{DOCUMENT_ROOT}public%{REQUEST_URI} -f
RewriteRule (.+) /public/$1 [L]

# route everything else to /public/index.php
RewriteRule ^ /public/index.php [L]

The slightly more complicated method

If your server doesn't set DOCUMENT_ROOT properly, then you'll need to use an absolute path in RewriteCond. That is, an absolute path on the server's filesystem. You can get it by copying the following script to the directory where your Laravel installation will reside and visiting its URL - i.e. http://example.com/get_doc_root.php.

get_doc_root.php

<?php
echo getcwd();

This should result in something like /var/www/example.com/web. Use the following .htaccess file and replace [[your path]] with the actual path you got.

.htaccess

RewriteEngine on

# serve existing files in the /public folder as if they were in /
RewriteCond [[your path]]/public%{REQUEST_URI} -f
RewriteRule (.+) /public/$1 [L]

# route everything else to /public/index.php
RewriteRule ^ /public/index.php [L]

In our example case, the RewriteCond line would look like this:

RewriteCond /var/www/example.com/web/public%{REQUEST_URI} -f
@azizullahaziz

This comment has been minimized.

Copy link

@azizullahaziz azizullahaziz commented May 15, 2019

none of the methods you explained not working for me

@marwan2

This comment has been minimized.

Copy link

@marwan2 marwan2 commented Sep 21, 2019

Thanks, 2nd method works for me

@kosciCZ

This comment has been minimized.

Copy link

@kosciCZ kosciCZ commented Apr 13, 2020

Hey, this worked great for me (first method), but I had trouble at first, when I was trying to setup this for a subdomain, seems like a stupid mistake but it took me way too long to figure it out. So if anybody else is struggling with this:
RewriteCond %{DOCUMENT_ROOT}/subdomain/public%{REQUEST_URI} -f
This is assuming that you have a folder in your document root that acts as a subdomain

@mikeSxz

This comment has been minimized.

Copy link

@mikeSxz mikeSxz commented Dec 27, 2020

First method fixed redirections but :-( now styles are not loading, any idea what i'm doing wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment