I have setup my first pomander deploy and after running :setup it seems to get hung on

* info deploy setting up environment

It looks like it has created the shared and releases directories, but nothing happens after that.

Also, if I remove $env->releases('true') it deletes the parent directory (one that I created, not pomander). Not sure if that's the intended action, seems off.

Hi, I'm used to Capistrano and deployers and really enjoy you built one made of PHP.

But I'm having an issue : the script can't connect through ssh to my server. I tried to set the key path with $env->key_path('/System/Users/Username/.ssh/id_rsa') but I'm still getting the "Unable to load RSA key" message. I digged a little in the source code. The loadKey method from phpseclib is always returning false, I can't figure out why.

How do you manage to make it work ? I'm having no trouble connecting through my console.

If remote deployments require passwords after the initial SSH connection, Pomander is currently unable to handle them.

It would be great if Pomander could auto-respond to these prompts with a password or key_password from the environment config, or if the prompt could be presented to the user to provide input.

I tried to deploy with pomander, but it fails with my working SSH Key. A plain ssh login works.

Error message:

 * abort ssh Unable to load RSA key.

Tried against ǜersion "pomander/pomander": "dev-master".

The head of my private key:

$ cat .ssh/id_rsa
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,E731CBEFD26F9C7560C79A3E7C53C516

I have code like this: $env->user('user'); $env->repository('repo'); $env->scm('svn'); $env->deploy_to('/var/web'); $env->key_path("key"); $env->app(array('server1.com','server2.com'));

When i run deploy:update this command perform deploy only on the first server in the list. It there some additional options that enables deploying process on multiple servers?

• git ls-remote don’t work on revision)
• don’t return avoid function abort()
• never composer:update on deploy always install (with ""update" you do not know exactly what is deployed)
• composer disable by default
• .git_ignore ".idea" (project of PHPStorm IDE)

Hello!

Sorry, if I have missed something, but is there in Pomander feature like :linked_dirs in Capistrano? This feature allows to put directories to shared folder and creates symlinks to these directories in the releases dirs.

There is a shared folder in Pomander, but I didn't find any option to create symlinks neigher in the docs, nor in the code.

Best regards

I'm trying out pomander, but I can't get it function. My config:

<?php 
$env->repository('http://<svn-repository>')
    ->releases(true)
    ->keep_releases(5)
    ->user('<me>')
    ->scm('svn')
    ->revision('trunk')
    //
    ->backup(true)
;

//
// If you are deploying your application to a remote server:
//
$env->deploy_to('/usr/src/build/pom/track');
$env->app('<internal ip>');

When trying to check the setup, I get the following error:

hermes:pom gp$ pom deploy:setup
(in <my dir>)
 * info target <host ip>
 * info deploy setting up environment
bash: git: command not found
 * abort fail aborted!

I'm not using git. git isn't on the server. But SVN is. And I am trying to use SVN.

Today this method does not work and I added the ability to update submodules. Just add $env->submodule(true/false)

I also changed the log in the revision method

the SSH2 extension, like proc_open, is garbage. So many bugs that I dropped it completely.

This pull request goes BACK to using phpseclib with some modifications:

1. send request-pty bits in $ssh->exec() to get a pty. woo!
2. return the exit status of the ssh command.

Things like host key checking work wonderfully.

Rollback are... well, weird. Need to support the following:

• $app->env->releases == true?
  • false
    • checkout previously deployed hash
  • true
    • remove current/failed release
    • if finalize was called, re-set the symlink
• db:merge has run and backup exists?
  • true
    • restore the latest backup.

In Cli.php TaskNotFoundException can be thrown by print_tasks method, so here variable $task_name will be undefined.

Unfortunately at this time no way to get missed task name here, but I've create PR to Phake in order to solve this.

Cataloging notes and ideas about being able to manage deployments to Heroku via Pomander.

This should be a straightforward process as Heroku takes care of nearly everything for us. Pomander just really needs to run the key deploy tasks with empty commands so that before/after hooks can be triggered, and anything special can be taken care of.

Notes:

Example Capistrano task for deploying to Heroku:

namespace :deploy do
  desc 'Deploy the app'
  task :production do
    app = "my-amazing-heroku-app-name"
    remote = "[email protected]:#{app}.git"

    system "heroku maintenance:on --app #{app}"
    system "git push #{remote} master"
    system "heroku run rake db:migrate --app #{app}"
    system "heroku maintenance:off --app #{app}"
  end
end

Using a Composer plugin to trigger pom heroku

Just rely on heroku run: heroku run vendor/bin/pom heroku

Hi Mike, I made ​​a change for authorized to clone in a directory that already exists. This need appears if the directory is an NFS mount (with Vagrant for example). You can not remove this mount point :( Thank you

This is a rather large re-vamp of how deployment stacks are built.

Not ready

Deployments with Pomander have a strict release/no-release structure with some options one of which being scm to help offer a more flexible means to deploy for all projects. Problem is there is no way to break out of this structure and create deployment paths for other things (i.e. Heroku, Docker)

This new way allows that to happen..

All deployment related tasks are driven by a Method object. The method ultimately controls exactly how a deployment works. The base Method class implements the standard release / no-release structure for deploying, rolling back, cleanup, finalize, etc. There are stubbed methods for setup_code and update_code that you can sub class and customize to your needs, or just implement all new methods.

Breaking changes:

This release will introduce some potential breaking changes for anyone that used the $app->env->scm object. That object is now replaced by method.

• [x] - Git method
• [x] - Subversion method
• [x] - Rsync method
• ~~[ ] - Heroku method~~ (later)
• [ ] - New tests with passing current tests

While a deploy is running, create a deploy.lock file so that subsequent deploys cannot be happening at the same time.

Things to look out for:

If a deploy fails, will it always be able to remove the deploy.lock file? If it cannot, people will be stuck without being able to deploy.