Go to file
Matt Lowe 96981b72c7 Added method to allow checking the source code once IonCube has run for
any un-encoded/encrypted files.
This checks against an array of file extens (used mainly to exclude
images and javascript etc.)
It also checks against an array of paths/filenames.
These 2 should maybe be combined into a single array?
If any files are found to not be encoded and havnt been excluded, then
user is prompted to confirm they wish to proced.
This is designed as a last confirmation that you have encoded all the
files that you need, and are not about to push unsecured files to a
server.
2013-11-22 13:03:37 +00:00
bin Big refactoring. Use of Namespaces and codestyles. PSR-0, PSR-1, PSR-2. 2013-11-06 12:44:05 -02:00
docs Abort Deployment when pre-deploy task fails. Addresses issue #29 2013-11-08 13:42:34 -02:00
Mage Added method to allow checking the source code once IonCube has run for 2013-11-22 13:03:37 +00:00
.gitignore Cleanup. 2011-11-24 19:36:04 -02:00
composer.json Update composer.json 2013-09-23 15:31:26 +02:00
LICENSE Reference to Spyc Library License. 2013-11-05 14:14:50 -02:00
README.md add documentation for installing via composer 2013-09-20 16:32:47 +02:00

Magallanes

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": {
        // ...
        "andres-montanez/magallanes": "dev-master"
        // ...
    }

Now tell composer to download the bundle by running the command:

$ php composer.phar update andres-montanez/magallanes

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 specifing to which hosts you want to deploy and what tasks to run (after, on, and before deploying). And you are done!

And what spells... tasks! What tasks has it built in?

Just a few, for now...

  • deployment/rsync - This task is for deploying your code to the remote servers.
  • scm/update - This task is for updating (git/svn) your base working copy.

But that's not all! You can create your own tasks, and execute commands on your working copy and in your deployed code! Also we are working on creating more built in tasks.

This is awesome! Where can I learn more?

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

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