Build strategy

I don't really have a link for you to read about, but I always compile everything locally. So I push all the changes to git and then I pull the build files to server. This means you don't have to install gulp and npm on your server if you don't use it anyway. It also means you don't have to download all the npm dependencies on your server. There are a lot of those dependencies.

Working with teams you might get issues with this since you all compile your files and you end up with different versions. Our solution to that is letting only one guy push the compiled assets to git.

Thank you @bobbybouwmann. That sounds a great way of doing. I work alone on this project so I directly push to a --bare repository on the server.

So, if I properly understood you suggest:

• Feature branch
• Merge to master
• Compile build & Co.
• Tag a release
• Push master (tag) to Github / or server

Then I use git hooks to perform my deploy strategy and some additional tasks...

Thxs

@jrean Exactly ;)