README

This is an old repository that is no longer used or maintained. We advice to no longer use this repository.

Original README can be found below:

TravisDeployer

Combine Deployer with Travis-CI to automatically deploy after a branch is merged and the build passes.

Expectations

First of all, we expect you to have the following ready:

1. A deploy.php set up in the project root as described in the Deployer docs.
2. Travis-CI is enabled and you have a .travis.yml in the project root.
3. You have composer to load php dependencies.

Installing

1. Add TravisDeployer to your project using composer running: composer require enrise/travisdeployer
2. Add the following code to your .travis.yml:

travisdeployer:                  # our deployer config
    verbose: false               # verbose output the deployment?
    branches:                    # what branches do you want to deploy?
        develop: develop         # deploys stage develop when merging into develop
        master: production       # deploys stage production when merging into master

after_success:                   # after your build succeeded (tests passed)
    - vendor/bin/travisdeployer  # Trigger the travis deployer

You can customise the branches and if you want to deploy verbose or not.

Deploying

Now every time you push code into your branches and the travis-ci build succeeds, the TravisDeployer deploy script is triggered. This script will deploy when:

• The build is green
• The build is NOT a PR
• The branch pushed to is in the branches list (provided in the travis config)

If all criteria are matched, deployer will be downloaded to your build, and will deploy your code to your server. What happens during the deployment is what you configured in your projects root deploy.php (the Deployer config).

===

TravisDeployer is brought to you by Rick van der Staaij and Stefan van Essen.