Alex

Can you please post complete deployment log from `rocketeer.phar deploy -v` command (with private information hidden) as Gist? Or if your project is public, then just share its repo url...

> attached files already. Still can't get used to the fact, that it's possible to attach any file GitHub issues now. Sorry. > But i will be always checking if...

The `AbstractPackageManager::hasManifest` method, that checks for existence of `composer.json` file works like this: 1. look if file exists in current release or remote server 2. if it doesn't look if...

So full path to rocketeer is `/usr/bin/rocketeer.phar` or just `/usr/bin/rocketeer`. And when you run the command you're: - in the project folder that will be deployed - that project has...

I'm using Rocketeer 2.1.2 and above workflow (when I have Rocketeer placed centrally on developer machine) also works without problems. Do you really have this folder structure in the folder...

I'm not sure, that this scenario was even supposed to work based on what I'm reading in docs. In fact does doesn't explicitly say where Rocketeer commands are supposed to...

I have no idea, because I myself haven't ever configured such thing in other deployment system. What I was after is configurable deployment solution, when multiple servers are involved. Probably...

Nice. Will wait for v3 version then.

The `migrate` task is called automatically as part of `deploy` task, when: 1. roles are enabled (the `use_roles` setting in config) 2. one of servers on connection has `db_role` flag...

That is cool in fact. Opens a way to have dynamically populated server list, like from AWS.