Back in the day people used (S)FTP to ‘deploy’ their code to production. Especially when working in teams this could have nasty side effects, like overwriting changes made by a team mate or losing a week’s worth of development by accident with a single ‘Save to FTP’-command. So everybody stopped using this, right?

Nowadays it is a lot more common to have some sort of versioning control in place (like Git or Subversion). This is quite an improvement to prevent losing changes (and having a backlog of changes), but you can do so much more!

In this talk I will show (and explain) how to use GitLab Pipelines to automatically build your code (where necessary), test your code, and deploy it to production. I have several examples:

- WordPress plugins deployment to a custom VPS
- Symfony 4 deployment to a custom VPS
- Deployment to Azure
- Deployment to Heroku

These will also show the difference between using FTP for deployment versus Git, which seems arbitrary, but can be a very big difference in terms of feedback you get in GitLab (which I will show for both).