What is the Best Practice to deploy Laravel on Server?

This is by no means the best practice, but why not push your changes to github and then just clone it again on your server?

@WBARNARD81 - That's what I am doing right now, but I am wondering if i have slightly changed in my code. Do I need to clone whole thing?

Yeah, I have the same issue and am also looking for an easier alternative, but I do not think there is, as even with Heroku (and my express apps), I have to clone the repository after changes.

Apologies, maybe someone else can give you a better solution.

Edit: You can also use WinSCP to just upload the one file, that you have changed. Not sure if this is the solution you are looking for...

Have a look at https://deployer.org/

This allows you to automate the whole deployment process and is really easy to use.

What you are looking for are git hooks. I don't know much about server setup myself but some research into git hooks should set you up. A quick Google search yielded this:

https://gist.github.com/noelboss/3fe13927025b89757f8fb12e9066f2fa

Although I don't know if this matches your exact use case.

There is a bit of varying advice in this thread, but this is pretty simple and should not be time consuming at all.

1. Make your changes locally, ideally using branches for new updates etc.
2. Push your changes to git
3. SSH into your server
4. Run git clone origin master.

Do not clone your repo again, do not ftp files, do not edit files directly on the server via nano aside from files in your gitignore.

This should only take you a couple minutes, one min to push and another to ssh and pull.