search

octopress / deploy

Deployment for Octopress and Jekyll blogs.
MIT License
75 stars 23 forks source link

Deploy multiple stages #57

Closed rzane closed 9 years ago

rzane commented 9 years ago

This PR allows for multiple deployment stages in a backwards compatible manner.

By default, it will look for a key named production in the config.

imathis commented 9 years ago

Thanks for your work on this! I'm sorry it's taken me so long to respond (I've been traveling and I'm just getting back into things). I'm not sure if this is something I want to change. Multiple deployment options are currently available by passing the configuration option (as you well know). I think managing different configurations in different files is probably a better pattern and deploying to them specifically.

octopress deploy --config _production.yml
octopress deploy --config _staging.yml

Why do you think it's better to manage them nested under a different keys in the same file?

rzane commented 9 years ago

The primary reason is that it allows you to merge YAML keys. Also, having just one file keeps things simple.

imathis commented 9 years ago

I see how using key merging avoids duplication of shared configurations but I like the idea that users can look at a file and read all their settings without having to do a mental merge to discern which values are overridden. I think in the end it will be simpler to manage deployment settings as separate files.

Thank you for the time you spend working on this. It means a lot to me that you'd help out trying to make this better.