a poorly drawn pomander...

Pomander

1. Introduce Pomander to your project

This will give you a deploy folder and a development.php environment to get you started.


$ pom init

# NOTE: If you get 'command not found' try vendor/bin/pom
	

The environment development is assumed to be your local machine and will act as such. This gives you the ability to automate your development environment to get up and running more easily.

If you want to deploy to a server, read on to step 2!

2. Configure your environments

Create as many environments as you like, and name them as you please. Stuff like staging and production are great, but you can really do whatever you would like.


$ touch deploy/experiment.php
	

Pomander is flexible enough to work with your environment.


<?php
  $env->user('deploy')
      ->repository('git@github.com:tamagokun/mikey-kong.git')
      ->deploy_to('/var/www/html')
      ->releases(true)
      ->app('wacky-experiment.test-node-1.rackspace.com')
  ;
	

Refer to the Settings guide for complete docmentation.

3. Prepare environment for deployment

This will create the proper directory structure for your deployments on the server, and yell at you if it doesn't have the proper permissions.


$ pom staging deploy:setup
	

4. Profit

$$$


$ pom staging deploy

 * info environment staging
 * info target ec2-54-227-42-2.compute-1.amazonaws.com
 * info deploy updating code
HEAD is now at ab476f8
 * info deploy cleaning up old releases
 * info complete deployed 20130820125941