Question - Parallel deploy and rollback

[rlacerda83]

Hello friends,

I need your help!

I have two cases to deploy, a production and other staging for testing.

My production environment has 3 servers and the staging has only one server.

How does the parallel deployment? It performs all commands on all machines? In the case of my deploy in production, would run composer and all tasks on all servers?

If so, it is not performative. Today we have a script that does to build the project locally, performs all tasks and then replicates only the code for all servers. You can do this with the rocketeers?

Another doubt that I was against the rollback. The rollback just change the symlink the current folder? Does not perform migrations? You can send failure notifications?

My problem here is that if there is a failure in a server I need to give a complete rollback, including code and database. If not I have cases where I have a code out of sync with the database, and that's too bad ...

Thanks!

[Anahkiasen]

Hi!

Trying to answer your questions:

1. Rocketeer currently does all three deployments at the same time indeed. There is no way to deploy locally to then transfer the files as you are currently doing, at least not automatically. Rocketeer does come with an rsync strategy so you could create hook on the before of that task to prepare your release and Rocketeer should then rsync it on all three servers.

There will be an official local deployment strategy in Rockteer 3.

2. The rollbacks indeed just swap the symlink, but you can hook on the after event of the Rollback task to perform additional operations