Deployment procedure

Magento can be complex to work with. And so is deploying Magento. You first have to get your code on the server. Then run `setup:di:compile`, `setup:static-content:deploy`, `setup:upgrade`. Or should you run `setup:upgrade` first? Ow no, we forgot to do a git pull, or we forgot to upload that one file. Do we have to do these steps over? Hey, what is this error? Why don't I have this on my local machine? Did I follow the correct order? `setup:upgrade` should go last, right? And while you are figuring out these steps, your site is unreachable for the rest of the world.

Does this sound like you? Know there is a better way. How about this:

• Do a git push to master.

• Wait an x amount of time (depends on a few factors).

That's it. We can let your pipeline do all the heavy lifting for you. It builds the Magento shop for you and prepares everything in the background. And then, when it's done, it switches over to the newly prepared version. In most cases, even without any downtime.

The minimum requirement for this is to use GIT, or be willing to use GIT. If you don't have the code stored in GIT yet, that's not an issue. We will handle this for you, too.