Hello, something I can't understand is how to integrate deployer into our setup.

Right now when we want to deploy some changes from local env to production, we need to make sure that git status on production is empty and than do git pull. That require login to production ssh, and additional git actions, if something was changed on production(theme files for example). The question is how we integrate tools like PHP Deployer for example, or Gitlab CI to automate deployments?

Last updated 3 years ago

Hi there.

This is more of a general question and the advice for any Laravel project would apply. The best approach would be to create a private git repository for your project, push the code there and use CI to deploy it to your staging, development, or production environments based on the branch name. You could even have custom environments for testing feature branches

daftspunk said:

Hi there.

This is more of a general question and the advice for any Laravel project would apply. The best approach would be to create a private git repository for your project, push the code there and use CI to deploy it to your staging, development, or production environments based on the branch name. You could even have custom environments for testing feature branches

Yeah, that's an option if you don't have files changed on production. Than you need to merge all this stuff somehow, and we all "love" and "trust" automerging