Go to file
Andrés Montañez 515f90950b Remove ENV Variables 2017-01-06 08:41:52 -03:00
Mage Remove ENV Variables 2017-01-06 08:41:52 -03:00
bin Release v1.0.7 2017-01-05 23:58:33 -03:00
build/logs Merge branch 'master' into develop 2017-01-05 22:56:11 -03:00
docs Merge pull request #184 from edpauto/env-vars-support 2015-05-19 10:35:36 +02:00
tests/MageTest FIX PSR2 2015-07-02 09:45:42 +02:00
.coveralls.yml Coveralls configuration 2015-02-19 20:39:49 +01:00
.gitignore Merge pull request #186 from d-ulyanov/develop 2015-01-30 08:34:14 +01:00
.travis.yml Dependencies 2017-01-05 23:37:13 -03:00
CONTRIBUTING.md Merge pull request #190 from edpauto/contribution-coverage 2015-02-08 18:53:13 -02:00
LICENSE Prepare for version 1.0.6 2015-04-12 16:45:32 -03:00
LICENSE_YAML Text files should end with a newline character. 2014-10-11 15:07:36 -02:00
README.md Fix Composer version constraint 2015-12-11 09:35:50 +01:00
box.json Add a box.json file to build PHAR 2014-10-01 07:49:46 +03:00
composer.json Dependencies 2017-01-05 23:43:28 -03:00
phpunit.xml.dist setting constant in phpunit config 2015-03-11 21:47:30 +01:00

README.md

Magallanes

SensioLabsInsight Build Status Coverage Status

What's Magallanes?

Magallanes is a deployment tool for PHP applications; it's quite simple to use and manage. It will get your application to a safe harbor.

So, What can it do?

You can instruct Magallanes to deploy your code to all the servers you want (via rsync over ssh), and run tasks for that freshly deployed code.

How can I install it via composer?

Simply add the following dependency to your projects composer.json file:

    "require-dev": {
        // ...
        "andres-montanez/magallanes": "~1.0"
        // ...
    }

Now tell we update the vendors:

$ php composer update andres-montanez/magallanes

And finally we can use Magallanes from the vendor's bin:

$ bin/mage version

System-wide installation with composer

$ composer global require "andres-montanez/magallanes=~1.0"

Make sure you have ~/.composer/vendor/bin/ in your path. You can now use Magallanes by using the mage command.

Can you give me some examples/ideas?

Sure! Suppose you have a checkout of your app and you have to deploy it to four servers; and after each deploy you have to run some boring tasks, like fixing file permissions, creating symlinks, etc. You can define all this on Magallanes and with just one command you can do all this at once!

Like this:

$ mage deploy to:production

What's this sorcery?!

Easy boy. It's not sorcery, just some technomagick!

In Magallanes you define environments like testing, staging, or production like on the example above. Then, on that environment, you can configure a setup specifying to which hosts you want to deploy and what tasks to run (after, on, and before deploying). And you are done!

This is awesome! Where can I learn more?

You can read the whole source code (naaah!); or checkout the documentation at: http://magephp.com

Enjoy your magic trip with Magallanes to the land of the easily deployable apps!!

"develop" branch

Please, all pull request now must be on the develop branch. Thanks!