Upload laravel project to shared hosting issue

See https://laracasts.com/discuss/channels/laravel/upload-project-laravel?page=1 and the links here https://laracasts.com/discuss/channels/laravel/env-file

Hi jlrdw,

have u read my whole problem ? Unfortunately i dont find anything useful from both links u gave me. :(

This article on my blog is hosting using the same structure http://novate.co.uk/deploy-laravel-5-on-shared-hosting-from-heart-internet/

Hi Snapey,

i have made the same things as you are writing in your blog, but i still get this error:

FatalErrorException in AuthServiceProvider.php line 42: Class 'Illuminate\Auth\AuthManager' not found

I have tried to include that class, but the error still appears

Reload http://stackoverflow.com/questions/28364496/laravel-5-remove-public-from-url And look at the last three answers, a combination of these last three answers is what works and do not use dotenv file, hard code all in config files. This works perfect on GoDaddy. I uploaded site using FTP there was no need to run composer on the production side.
Also why isn't the whole laravel site under the subdomain?

Check the case of the filenames. Its not uncommon to have a local development environment where case does not matter, and then when you upload to a system that is case sensitive, files are 'missing'.

@jlrdw best to keep the site and framework out of the public space else you risk security issues.

Unfortunately this 'Illuminate\Auth\AuthManager' i have never used. It is used in the 'Illuminate/Auth/AuthServiceProvider.php', but there i have never made any changes.

Could "composer global update" change anything to my local project and then to upload it to the webserver ?

In your FileViewFinder.php at line 137 you are calling a view named 'layouts.front'?

The error gives this path /home/bgfreela/laravel/resources/views/front/index/show.blade.php with which I understand layouts.front is a directory, not a view. You shouldn't call 'layouts.front.index.show' instead?

This error is fixed. But the problem with the AuthManager is still there :(

Have you properly resolved your paths?

jlrdw, if you mean the paths in config/app.php and public/index.php - yes.

Did I misunderstand you did you actually have Part of laravel installed on a domain and another part in a subdomain? It would be so much easier on you if you put the whole thing in the subdomain, you can still put the main files higher than public for safety but again I may have misunderstood you.
If you follow the steps that @Qlic gave it works.

The laravel core (everything except the public folder) is in the root (on the same level as public_html) of my web server. Everything from the public folder i have put in the subdomain folder (public_html/subdomain). I hade problems, that some of my views were in the public folder, thats why came the error : ErrorException in FileViewFinder.php line 137: View [layouts.front] not found. But i moved these files to the laravel resources, so that error disappear, but i still get the error: Class 'Illuminate\Auth\AuthManager' not found, which is very strange for me.

The laravel core (everything except the public folder) is in the root (on the same level as public_html) of my web server.

... then you have not followed the structure I suggested in my article. You will therefore have issues such as mentioned, in addition if you are using .env file someone can just go to yoursite.com/.env and see all your settings.

No, there is no such danger. The .env file is not in the public_html folder, it is one level above. Maybe i was not very

etc/ laravel/ public_html/ .env