Laravel Deployment on Shared Hosting

@Sinnbeck I divide my laravel project into 2 folders (i do this so the user can't check out my .env file):

1. laravel (all laravel files except public)
2. public (I moved all the contents of the file to public_html)

Based on your second solution, do I have to move the laravel folder to public_html? then do something with htaccess file?

@oka_ Set up laravel with correct folder structure and point to public as document root.

Another technique (advanced) is:

http://novate.co.uk/deploy-laravel-5-on-shared-hosting-from-heart-internet/

@oka_ Yeah move everything into public_html and add a htaccess file that tell its to use /public as root. And double check that you cannot access .env or /storage as they will be left open (but can be denied in htaccess)

Something like

RewriteEngine On 

#Rewrite everything to https
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

#Rewrite everything to subfolder 
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/public
Rewriterule ^(.*)$ public/ [L]

@Sinnbeck am I have to delete the previous htaccess?

@oka_ Is there already one inside the public_html folder?

@jlrdw is the user can see my .env file if I set it back to the correct structure?

@Sinnbeck yes, it's like this:

<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>

@oka_ As far as I know this htaccess should deny all folders and files that isnt /public (I dont use shared hosting myself, so I just borrowed the example from another thread)

@oka_ That looks like the one from /public? Do you have the same file in both places?

@Sinnbeck /home/myWebsite

+...

+...

-public_html
	(there's only one htaccess file)

+...

It's my routes I guess, so there's only one htaccess file on it. (htaccess & index.php is in the same folder)

@Sinnbeck I wonder about the structure of the /public you said, it's public/public_html or public_html/public ?? I'll try to make it as a root, but I'm getting confused about the structure

@oka_ The way my suggestion 2 is

- public_html
   - new .htaccess from above
   - ... all of your laravel files and directories unedited

So its /public_html/public. But as I said, all files and folders. Not just public

@Sinnbeck Okay I did that, now I got an internal error like this (i guess the problem is on my htaccess file now):

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at (my webmaster mail) to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.