Framework Install / Production System ?

Firstly Laravel has a public/ folder that should be the webroot of the app, that means if your servers structure is something like this: /home/mysite.com/public_html then you could do with uploading the app to /home/mysite.com and taking a look at https://laracasts.com/discuss/channels/general-discussion/where-do-you-set-public-directory-laravel-5 or altering your Apache config to point to public/ instead of public_html/

A general deploy looks something like this:

• Upload the files
• Run composer install
• Run npm install && gulp --production (if they're not compiling their assets locally)
• Configure the environment in %project_path%/.env (see .env.example)
• Run database migrations (php artisan db:migrate)

Lets say for example....I don't have composer or laravel framework installed on the production server.

Those are installed on the development server setup. They are using BitBucket to store their code.

On the production server if I Pull the code down. Everything from the Application directory including the "public" folder.

Then have apache use that public folder as its document root.

Would this work?

I really don't wnat to run framework commands on the production system. All framework or files needed are under the application directory correct ?

Thanks.

If you follow @Qlic guide from this post, that will get up up to snuff. https://laracasts.com/discuss/channels/laravel/upload-project-laravel