search

scttnlsn / dandelion

Incremental Git repository deployment.
http://scttnlsn.github.io/dandelion
MIT License
738 stars 57 forks source link

Support for multiple servers #35

Closed chluther closed 11 years ago

chluther commented 11 years ago

I'm trying out dandelion for a situation where I only have FTP access to the server. Is there support for multiple servers - for example a STAGE and PRODUCTION server? If so, how to configure?

jamesmoss commented 11 years ago

There's no support for multiple servers.

You could write a wrapper around dandelion which generates a temporary config file, points dandelion towards it using --config and then removes it. We've done this for our deploys and it works well.

chluther commented 11 years ago

thank you for the quick response!! Alternatively, could I not also perform dandelion --config=stage.yml deploy?

Related issue: Is it possible to specify a branch, e.g.: feature/sprint1 . I've found the --repo= option, but don't know yet if it supports deployment from anything other than HEAD.

jamesmoss commented 11 years ago

Alternatively, could I not also perform dandelion --config=stage.yml deploy?

Yep of course.

Dandelion only supports deploying from HEAD - again we added something to the wrapper at my workplace to checkout a branch before deploying to staging.

scttnlsn commented 11 years ago

@chluther What sort of errors are you seeing when you run dandelion --config=stage.yml deploy?

Also, I think deploying from a ref other than HEAD might be a nice feature.

scttnlsn commented 11 years ago

The deploy command accepts a revision argument like:

dandelion deploy 173c5edc8f

Depending on what https://github.com/mojombo/grit supports this might actually be possible as is.

chluther commented 11 years ago

Well I may be a little confused with dandelion's operation. I'm working with my GIT repository, using GIT-FLOW to manage fairly standard master / develop / feature branches. I've checked out and I'm working on my Feature branch. Commit changes to the branch. But when I run dandelion deploy it does not seem to get the most recent changes in the feature branch. No deploy errors - all seemed to go well. Hmmm.

scttnlsn commented 11 years ago

Unfortunately I cannot reproduce what you describe. When no revision is specified Dandelion with deploy the HEAD revision. If you have your feature branch checked out then HEAD should point to the latest commit on that branch. Alternatively, you could explicitly specify the commit you wish to deploy:

dandelion deploy my-feature-branch

Which will deploy the latest commit on my-feature-branch even if you have master checked out.

chluther commented 11 years ago

Thank you for your reply. I was able to track my issue down to a misconfigured PATH in my .YML file. I have since verified that deploy my-feature-branch does work.

scttnlsn commented 11 years ago

Great!