Skip to content

Latest commit

 

History

History
65 lines (49 loc) · 3.08 KB

Deploying.md

File metadata and controls

65 lines (49 loc) · 3.08 KB

Deploying

Basic deployment

Once your credentials are properly setup after the Getting Started section, it's time to deploy your project.

If it's your first time deploying on the server, call the rocketeer deploy command, it'll setup your server and deploy for the first time. Depending on what strategy you picked, it will either clone or rsync your project on the server. You can choose to only deploy to specific servers or stages by using the relevant flags:

$ rocketeer deploy
$ rocketeer deploy --on="staging,production"
$ rocketeer deploy --on="production" --stage="staging"

Once a first release is properly setup, to speed things up you can decide to use the Update task, which will not create a new release, but simply update the current one:

$ rocketeer update

The same options can be used as above. Per example if you use the Clone strategy, it will do a git pull on the current release, and re-run any relevant event listeners you created.

Dry runs

If you're unsure about your deployment procedure, you can use the --pretend flag to display what commands and tasks would be run were you to execute the command normally.

$ rocketeer deploy --pretend
|-- Running: Deploy (Deploys the website) [~14.25s]
|---- Running: Primer (Run local checks to ensure deploy can proceed)
|---- Running: CreateRelease (Creates a new release on the server) [~5.98s]
|------ Running strategy for Deploy: Sync
$ mkdir /home/www/myapp/releases/20140817160632
$ rsync ./ host@server:/home/www/myapp/releases/20140817160632 --verbose --recursive --rsh="ssh" --exclude=".git" --exclude="vendor"
|---- Running: Dependencies (Installs or update the dependencies on server) [~5.15s]
|------ Running strategy for Dependencies: Composer
$ cd /home/www/myapp/releases/20140817160632
$ /usr/local/bin/composer install --no-interaction --no-dev --prefer-dist
|---- Running: Migrate (Migrates and/or seed the database) [~0.21s]
|------ Running strategy for Migrate: Artisan
$ mv /home/www/myapp/current /home/www/myapp/releases/20140817160632
$ rm -rf /home/www/myapp/current
$ ln -s /home/www/myapp/releases/20140817160632 /home/www/myapp/current
Successfully deployed release 20140817160632
|-- Running: Cleanup (Clean up old releases from the server) [~2.68s]
$ rm -rf /home/www/myapp/releases/20140817135635
Removing 1 release from the server
Execution time: 3.5601s

Parallel deployments

By default Rocketeer executes everything synchronously, but via the --parallel flag you can decide to deploy everything in parallel. An important note on what this means: it will not run tasks within a queue in parallel, the order of tasks in a queue is crucial and thus that order is kept. What it will run in parallel, is the various connections and/or stages.

Say you have the following task registered:

Rocketeer::task('some-task', ['foo', 'bar']);

If you have 3 connections, each with 2 servers and 2 stages, Rocketeer will spawn 12 processes in parallel, each doing sequentially foo then bar on the matching connections/stages.